Last Modified: Feb 05, 2026
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Dec 19, 2025 Severity: 3-Major
If an internal chassis network partition causes the chassis partition HA pair to go active/active, the HA pair will resolve to the current preferred controller when the network partition is fixed. But future attempts to manually fail over to the other controller using the 'go-standby' command will immediately fail back to the original controller.
The go-standby command will not work.
If an internal controller network partition causes partition HA pair to go active/active the internal failover state is left inconsistent.
Proper operation can be restored by restarting the partition HA on the non-preferred controller (controller-2 if in 'auto' mode): syscon-1-active(config)# system diagnostics os-utils docker restart node controller-2 service partition1_ha Restarting container affects configuration and data path. Do you want to proceed? [yes/no] yes result partition1_ha restarted successfully syscon-1-active(config)#
None