Bug ID 904713: FailoverState device status and CM device status do not match shortly after triggering failover

Last Modified: May 20, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP SSLO(all modules)

Opened: Apr 29, 2020
Severity: 3-Major

Symptoms

After triggering failover, the result returned by the API endpoint /mgmt/tm/shared/bigip-failover-state (the BIG-IP failover state worker) may not match the actual device failover state.

Impact

Actions that require the correct output of the BIG-IP failover state worker may fail. For instance, deleting an SSL Orchestrator topology followed by immediately triggering failover may encounter this issue, causing the deletion to fail.

Conditions

This may happen on an high availability (HA) setup with a sync-failover device group.

Workaround

After waiting for a short amount of time, the BIG-IP failover state worker will be in sync with the device failover state. So in the example of deleting an SSL Orchestrator topology, the deletion should be successful if you try again after a short wait.

Fix Information

None

Behavior Change