Bug ID 1754997: Tenant instance may fail to come up after repeated blade reboots.

Last Modified: Jun 19, 2025

Affected Product(s):
F5OS F5OS-C(all modules)

Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1

Opened: Nov 25, 2024

Severity: 2-Critical

Symptoms

A tenant instance may fail to come up to running in the BIG-IP cluster after repeated reboots of the blade hosting the tenant instance. In this case the blade will show as offline in the "show sys cluster" output. --------------------------------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Alt-Address Availability State Licensed HA Clusterd Reason --------------------------------------------------------------------------------------------------------- | 1 :: :: offline enabled false unknown shutdown Slot Failed | 2 :: :: available enabled true active running Run | 3 :: :: unknown enabled false unknown shutdown Slot powered off or empty | 4 :: :: unknown enabled false unknown shutdown Slot powered off or empty | 5 :: :: unknown enabled false unknown shutdown Slot powered off or empty | 6 :: :: unknown enabled false unknown shutdown Slot powered off or empty | 7 :: :: unknown enabled false unknown shutdown Slot powered off or empty | 8 :: :: unknown enabled false unknown shutdown Slot powered off or empty

Impact

The affected tenant instance will be inoperable until the blade is rebooted again to recover.

Conditions

Repeated reboots of the blade hosting the BIG-IP tenant instance.

Workaround

Rebooting the blade while the instance is in the impacted state will restore the tenant instance.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips