Last Modified: Dec 17, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.5.1.2, 17.5.1.3, 21.0.0
Opened: Oct 10, 2025 Severity: 2-Critical
Running 'tmsh reboot slot all' on multi-slot tenant or vCMP guest or VIPRION causes BIG-IP to get stuck in unhealthy state. MCPD is failing to load with the error '01070710:3: Could not find master-key object': slot3/tenant1.example.com notice clusterd[7956]: 013a0024:5: Blade 3: Changing primary from 0 (none) to 2 slot3/tenant1.example.com err clusterd[7956]: 013a0018:3: Blade 3 turned RED: Quorum: stepping slow clock forward by 747.133704 ms, HA TABLE offline slot3/tenant1.example.com notice clusterd[7956]: 013a0006:5: Blade status: 0 GREEN 1 YELLOW 1 Not Ready slot1/tenant1.example.com notice mcpd[4785]: 01070419:5: Platform initialization phase triggered. slot2/tenant1.example.com emerg load_config_files[9951]: "/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@rdt2:/S1-red-P::INOPERATIVE:Standalone] config # tmsh show sys cluster ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address 10.0.0.2/16 Alt-Address :: Availability available State enabled Reason Cluster Enabled Primary Slot ID 1 Primary Selection Time 11/01/25 18:06:26 ----------------------------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Alt-Address Availability State Licensed HA Clusterd Reason ----------------------------------------------------------------------------------------------------- | 1 :: :: offline enabled true offline running Run, HA TABLE offline | 2 :: :: offline enabled false offline running Run, HA TABLE offline
All tenant or guest slots remain offline, and are inoperable from a traffic standpoint.
1. Multi-slot F5OS tenant or Multi-slot vCMP guest or multi-bladed VIPRION. 2. Rebooting all the slots of the guest or tenant (e.g. 'tmsh reboot slot all' or 'clsh reboot')
For both tenants and guests, re-deploying them has a high probability of resolving the issue. That is changing the tenant's or guest's state from "deployed" to "provisioned" or "configured", and then back to "deployed". or Restarting mcpd on the primary slot also has a high probability of resolving the issue. Tmsh show sys cluster will report the "Primary Slot ID" # tmsh show sys cluster ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address address Alt-Address :: Availability available State enabled Reason Cluster Enabled Primary Slot ID 1 Primary Selection Time 11/01/25 18:06:26 Both workarounds are highly likely to restore the tenant or guest to full functionality. Note: the issue might return if all tenant or guest slots are rebooted.
None