At a loss on network config chicken/egg

MilitaryNerd

Hi everyone,

I'm really stuck on how to move forward here. From what I can tell, bond0 is gone from the configuration (doesn't show in the UI and I can't find a UID for it). However, all the PIFs still reference that they are channel members and when I try to add them to a new bonded interface, I get the following error:

network.createBonded
{
  "bondMode": "lacp",
  "description": "",
  "mtu": "",
  "name": "bond1",
  "pifs": [
    "74eb9410-ccbd-06dd-2b2d-85ace88ab94e",
    "69468fbf-db2d-1166-f7e0-1ed380048ca0",
    "748543b8-8f4d-de65-8a45-a44d0eb09dcb",
    "5f9fc097-6b6e-e5dc-f643-15a3cb4698c2"
  ],
  "pool": "bbbf33eb-abd4-b6d6-0511-fa6b7196d43a"
}
{
  "code": "PIF_CONFIGURATION_ERROR",
  "params": [
    "OpaqueRef:f97a8a6d-392f-4ac4-b8d4-9e09a8e926e7",
    "script error [script = /usr/bin/ovs-vsctl, args = --timeout=20 -- --may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4 -- set port bond0 MAC=\"00:0a:f7:4a:b3:a8\" lacp=active bond_mode=balance-tcp bond_updelay=31000 bond_downdelay=200 other-config:bond-miimon-interval=100 other-config:bond-detect-mode=carrier other-config:lacp-time=\"slow\" other-config:lacp-fallback-ab=\"true\", code = Exit code 1, stdout = , stderr = ovs-vsctl: \"--may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4\" but bond0 is actually attached to bridge xapi0
]"
  ],
  "call": {
    "method": "Bond.create",
    "params": [
      "OpaqueRef:cc471c99-c887-4e3c-91c7-0b736cb883f6",
      [
        "OpaqueRef:43976fd1-cdcb-4778-91cd-6908260482e3",
        "OpaqueRef:de967689-677a-4a3e-bab8-6d33cba095f8",
        "OpaqueRef:665f5a69-b35c-4819-98a9-d0bd211249a1",
        "OpaqueRef:44d8acaf-f0ce-4652-870d-a0041a6e6004"
      ],
      "",
      "lacp"
    ]
  },
  "message": "PIF_CONFIGURATION_ERROR(OpaqueRef:f97a8a6d-392f-4ac4-b8d4-9e09a8e926e7, script error [script = /usr/bin/ovs-vsctl, args = --timeout=20 -- --may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4 -- set port bond0 MAC=\"00:0a:f7:4a:b3:a8\" lacp=active bond_mode=balance-tcp bond_updelay=31000 bond_downdelay=200 other-config:bond-miimon-interval=100 other-config:bond-detect-mode=carrier other-config:lacp-time=\"slow\" other-config:lacp-fallback-ab=\"true\", code = Exit code 1, stdout = , stderr = ovs-vsctl: \"--may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4\" but bond0 is actually attached to bridge xapi0
])",
  "name": "XapiError",
  "stack": "XapiError: PIF_CONFIGURATION_ERROR(OpaqueRef:f97a8a6d-392f-4ac4-b8d4-9e09a8e926e7, script error [script = /usr/bin/ovs-vsctl, args = --timeout=20 -- --may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4 -- set port bond0 MAC=\"00:0a:f7:4a:b3:a8\" lacp=active bond_mode=balance-tcp bond_updelay=31000 bond_downdelay=200 other-config:bond-miimon-interval=100 other-config:bond-detect-mode=carrier other-config:lacp-time=\"slow\" other-config:lacp-fallback-ab=\"true\", code = Exit code 1, stdout = , stderr = ovs-vsctl: \"--may-exist add-bond xapi9 bond0 eth7 eth6 eth5 eth4\" but bond0 is actually attached to bridge xapi0
])
    at Function.wrap (/opt/xo/xo-builds/xen-orchestra-202206110404/packages/xen-api/src/_XapiError.js:16:12)
    at /opt/xo/xo-builds/xen-orchestra-202206110404/packages/xen-api/src/transports/json-rpc.js:37:27
    at AsyncResource.runInAsyncScope (node:async_hooks:202:9)
    at cb (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/util.js:355:42)
    at tryCatcher (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xo/xo-builds/xen-orchestra-202206110404/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

Any direction would be so helpful, thank you!

olivierlambert

Hmm doesn't ring any bell to me
@fohdeesha what do you think?

fohdeesha

@MilitaryNerd Have you restarted the host since removing this bond? It's reporting that bond0 is still attached to an OVS bridge, so it may need a reboot. You can also ensure the bond is really gone by running xe bond-list, it should return nothing. You could also still have the bond PIF existing or other networks using the old bond, check that you don't have any PIFs with device ( RO): bond0 listed when running xe pif-list