Bug ID 2229345: F5OS VELOS: Stale blade configuration causes tenant reboot when removing empty slots

Last Modified: Mar 04, 2026

Affected Product(s):
F5OS Install/Upgrade, Velos(all modules)

Known Affected Versions:
F5OS-C 1.8.2

Opened: Feb 26, 2026

Severity: 3-Major

Symptoms

Removing empty slots from partition causes unexpected tenant reboot. Physically absent blade remains in OpenShift cluster, blocking F5OS upgrade completion until the slot is moved to the 'none' partition, triggering forced kubevirt reinstall and tenant redeployment.

Impact

Unexpected tenant reboot and service disruption when removing empty slots. F5OS upgrade is stuck in an inconsistent state until the stale configuration issue is resolved.

Conditions

-- Blade is physically removed but not cleaned from OpenShift cluster -- F5OS upgrade performed with stale blade configuration present -- Empty slots subsequently removed from the partition.

Workaround

Move the affected slot to the 'none' partition.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips