Bug ID 1574573: Global Resiliency Group status not reflecting correctly on update

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.2.0, 20.2.1

Opened: Mar 29, 2024

Severity: 3-Major

Symptoms

After updating the Global Resiliency group, the group status may not immediately switch to "DEPLOYING," potentially causing the UI to inaccurately reflect the ongoing provisioning process, despite deployment being in progress.

Impact

Update Status of Global Resiliency Group is incorrect.

Conditions

During updates to the Global Resiliency group.

Workaround

To mitigate this issue, wait for approximately 5 minutes after updating the Global Resiliency group. This will allow the DNS listener address to become available for the newly added instance.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips