Last Modified: Apr 28, 2023
Known Affected Versions:
16.0.0, 188.8.131.52, 16.0.1, 184.108.40.206, 220.127.116.11, 16.1.0, 16.1.1, 16.1.2, 18.104.22.168, 22.214.171.124, 16.1.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Apr 29, 2020 Severity: 3-Major
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.
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.
This may happen on an high availability (HA) setup with a sync-failover device group.
After waiting for a short amount of time, the BIG-IP failover state worker gets 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.