Bug ID 1399369: While upgrading or rebooting an rSeries appliance that is running a standby BIG-IP tenant, the tenant goes active, causing the active peer tenant to go standby

Last Modified: Jan 07, 2026

Affected Product(s):
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
F5OS-A 1.7.0, F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3

Opened: Nov 16, 2023

Severity: 1-Blocking

Symptoms

BIG-IP tenant that is running on appliance that goes down for reboot becomes active, causing current active peer tenant to go briefly standby.

Impact

Traffic impact is observed until the newly active tenant stops and the peer tenant returns to the desired active state. Typically up to two minutes.

Conditions

-- BIG-IP tenants running on F5OS -- Appliance that is running a standby tenant is rebooted (e.g., during an upgrade) -- Management IP is not used for network failover

Workaround

Prior to rebooting or upgrading the appliance: -- Stop the standby tenant (for example, set tenant's running-state to Configured or Provisioned from F5OS) -- Or force offline the standby tenant Or configure network failure with management IP as per https://my.f5.com/manage/s/article/K14135

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips