Bug ID 1696269: If partition confd initiates a failover due to a health fault, it may incorrectly attempt to fail over repeatedly

Last Modified: Jun 16, 2025

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-C 1.6.2

Fixed In:
F5OS-C 1.8.0

Opened: Oct 14, 2024

Severity: 3-Major

Symptoms

In some conditions, when the partition confd initiates a failover to the other controller, it fails to complete the failover in a timely fashion and the original instance reclaims the active role. If the failover was due to a controller fault and is still present, it will immediately fail over again.

Impact

While the partition instance is failing back and forth, the control-plane functions are unavailable or degraded, and this can impact dataplane operations.

Conditions

If a controller health fault is present on system controller-1, and the partition redundancy mode is set to either "auto" or "prefer-1".

Workaround

Set the partition "system redundancy config mode" to "active-controller". When a controller fault exists, and the controller fails over, the partition will automatically prefer to follow the active controller location.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips