Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on sdnController.createPrivateNetwork #8027

Open
gkirk90 opened this issue Sep 30, 2024 · 13 comments
Open

Error on sdnController.createPrivateNetwork #8027

gkirk90 opened this issue Sep 30, 2024 · 13 comments

Comments

@gkirk90
Copy link

gkirk90 commented Sep 30, 2024

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

stable

Provide your commit number

cc3d5

Describe the bug

Error when trying to create a private network. Appears no PIF is found on 1 of my 7 hosts. All 6 others are fine.

Error message

{
  "generatedMessage": false,
  "code": "ERR_ASSERTION",
  "actual": false,
  "expected": true,
  "operator": "==",
  "message": "No PIF found",
  "name": "AssertionError",
  "stack": "AssertionError [ERR_ASSERTION]: No PIF found\n    at PrivateNetwork.addHost (/opt/xen-orchestra/packages/xo-server-sdn-controller/src/private-network/private-network.js:70:11)\n    at map (/opt/xen-orchestra/packages/xo-server-sdn-controller/src/private-network/private-network.js:149:57)\n    at Array.map (<anonymous>)\n    at PrivateNetwork.electNewCenter (/opt/xen-orchestra/packages/xo-server-sdn-controller/src/private-network/private-network.js:149:40)\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at processImmediate (node:internal/timers:454:9)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)\n    at SDNController._createPrivateNetwork (/opt/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:770:7)\n    at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:169:22)\n    at Task.run (/opt/xen-orchestra/@vates/task/index.js:153:20)\n    at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:389:20)"
}

To reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Expected behavior

New Private network connected without error.

Screenshots

No response

Node

16.12.1

Hypervisor

XCP-ng 8.2.1

Additional context

No response

@olivierlambert
Copy link
Member

Hi,

  1. Please follow instructions here first: https://xen-orchestra.com/docs/community.html (ie get on latest commit first).
  2. Check that you have the same number of PIFs/same NIC order between your hosts in your pool (assuming they are similar machines?)

Adding @benjamreis in the loop here.

@gkirk90
Copy link
Author

gkirk90 commented Sep 30, 2024 via email

@benjamreis
Copy link
Contributor

Hello!

1st things 1st: can you check that the PIFs are attached to the host?
To list the PIFs you need to run xe pif-list network-uuid=<uuid of network of selected PIF>

@gkirk90
Copy link
Author

gkirk90 commented Oct 1, 2024 via email

@benjamreis
Copy link
Contributor

Are the PIFs' IP configured or does the pif on the 7th host have no IP configuration?
There should be more info in error in XO.

@gkirk90
Copy link
Author

gkirk90 commented Oct 2, 2024 via email

@gkirk90
Copy link
Author

gkirk90 commented Oct 2, 2024 via email

@benjamreis
Copy link
Contributor

the issue is the bond0 thing indeed. because the device needs to be the same on all hosts.

@gkirk90
Copy link
Author

gkirk90 commented Oct 2, 2024 via email

@benjamreis
Copy link
Contributor

benjamreis commented Oct 2, 2024

Hmm since the device is read-only in a PIf IDK except from recreating the network.
But I don't unbderstand how one host has bond0 and the other have bond1.

@gkirk90
Copy link
Author

gkirk90 commented Oct 2, 2024 via email

@benjamreis
Copy link
Contributor

the naming bondX comes from XAPI
maybe the 7th host was joined later in the pool? and there already was a bond0 on the other?
Do the other hosts have a bond0 now on another network?

@gkirk90
Copy link
Author

gkirk90 commented Oct 2, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants