Last Modified: Oct 20, 2026
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.8.2, F5OS-C 1.8.2-HR1, F5OS-C 1.8.2-HR2, F5OS-C 1.8.2-HR3
Opened: Aug 04, 2026 Severity: 3-Major
When a blade running tenants configured with a mgmt-vlan is rebooted, sometimes the team0.xxx links on the blade do not get re-created after the reboot. Tenants fail to return to Running state on the slot in question, remaining in status "Not ready: containers with unready status: [compute]": ('show tenants') INSTANCE TENANT NODE POD NAME ID SLOT PHASE CREATION TIME READY TIME STATUS MGMT MAC ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 tenant01-1 1 1 Running 2026-08-03T10:10:01Z 2026-08-03T10:10:44Z Started tenant instance e6:82:d4:4a:c4:70 2 tenant01-2 2 2 Pending 2026-08-03T10:18:45Z 2026-08-03T10:18:45Z Not ready: containers with unready status: [compute] 00:00:00:00:00:00 The tenant's virt-launcher pod is stuck in ContainerCreating state: ('oc get pods --all-namespaces -o wide | grep virt-launcher') partition-3 virt-launcher-tenant01-1-pzb7l 1/1 Running 0 22h <none> blade-1.chassis.local partition-3 virt-launcher-tenant01-2-cmcxx 0/1 ContainerCreating 0 19h 100.79.0.140 blade-2.chassis.local Blade's /var/log/messages contains many entries similar to the following: Multus: [partition-3/virt-launcher-tenant01-2-cmcxx]: error adding container to network \"mgmt-conf-tenant01\": delegateAdd: error invoking conflistAdd - \"mgmt-conf-tenant01\": conflistAdd: error in getting result from AddNetworkList: failed to lookup master \"team0.54\": Link not found" The link in question does not appear in the blade's interface list: ('ip --br link | grep team0') team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.3@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.19@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.4@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.53@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.56@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.58@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP> team0.59@team0 UP 14:a9:d0:c4:20:72 <BROADCAST,MULTICAST,UP,LOWER_UP>
-- Multus is unable to bind the NetworkAttachmentDefinition for the tenant's management interface, preventing the tenant from starting up and reaching Running state. -- Blade logs are flooded with Multus errors.
-- mgmt-vlan configured on multiple tenants. -- Reboot a blade while the tenants are in deployed state.
To recover, move the affected tenants to Configured running-state, then back to Deployed. To avoid this issue, un-configure mgmt-vlan from the tenants in question (if possible): conf no tenants tenant <tenant> config mgmt-vlan commit Or move the tenants to Configured running-state, prior to a planned blade reboot.
None