Bug ID 2229881: Multi-slot tenant may become inoperative after tenant upgrade followed by tmsh reboot slot all

Last Modified: Apr 09, 2026

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.5.1.3, 17.5.1.4, 17.5.1.5

Opened: Feb 27, 2026

Severity: 2-Critical

Symptoms

After upgrading the tenant, if the command tmsh reboot slot all is executed on a multi-slot tenant, the tenant may fail to come back to an operational state and remain stuck in an inoperative state. Load sys configuration process fails with the error: Could not find master-key object slot2/tenant1 err tmsh[10271]: 01420006:3: Loading configuration process failed. slot2/tenant1 emerg load_config_files[10255]: "/usr/bin/tmsh -n -g -a load sys config partitions all base " - failed. -- 01070710:3: Could not find master-key object - sys/validation/MasterKey.cpp, line 3070 All slots will have an Availability of "offline" as reported in tmsh show sys cluster: root@tenant1:/S2-red-P::INOPERATIVE:Standalone] config # tmsh show sys cluster ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address 10.144.192.210/22 Alt-Address :: Availability available State enabled Reason Cluster Enabled Primary Slot ID 2 Primary Selection Time 02/26/26 15:23:52 --------------------------------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Alt-Address Availability State Licensed HA Clusterd Reason --------------------------------------------------------------------------------------------------------- | 1 :: :: offline enabled false offline running Run, HA TABLE offline | 2 :: :: offline enabled true offline running Run, HA TABLE offline | 3 :: :: offline enabled false offline running Run, HA TABLE offline Mcpd state will be base-config-load-failed [root@tenant1:/S2-red-P::INOPERATIVE:Standalone] config # tmsh show sys mcp-state ------------------------------------------------------- Sys::mcpd State: ------------------------------------------------------- Running Phase platform Last Configuration Load Status base-config-load-failed End Platform ID Received true Cluster Quorum Reached true

Impact

All slots remain offline and are inoperable from a traffic processing standpoint. Additionally, loading the system configuration fails

Conditions

1. A tenant upgrade is performed on a multi-slot F5OS tenant. 2. All slots of the tenant are rebooted using tmsh reboot slot all or clsh reboot.

Workaround

To bring the system back to a working state: reboot the current primary slot to change the primary slot, and then restart mcpd on the new primary slot using command: bigstart restart mcpd tmsh show sys cluster will report the "Primary Slot ID" # tmsh show sys cluster ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address 10.144.192.210/22 Alt-Address :: Availability available State enabled Reason Cluster Enabled Primary Slot ID 2 Primary Selection Time 02/26/26 15:23:52

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips