Bug ID 1750397: The system reached the maximum wait time for gossip worker to sync-oAuth Discovery failure.

Last Modified: Jun 28, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2

Opened: Nov 15, 2024

Severity: 3-Major

Symptoms

OAuth auto-discovery stops working after failover. Eventually an error occurs on the standby device "The system reached the maximum wait time for gossip worker to sync".

Impact

Fails to sync between active and stand by devices.

Conditions

A failover occurs while the OAuth auto discovery task is in SLEEP_AND_RUN_AGAIN state restcurl -X GET tm/access/oidc/discover

Workaround

To resolve gossip conflicts you can use any of below 3 workarounds. 1. Use the ha-sync/sslofix script 2. Run the following commands on both active and standby. restcurl -X DELETE shared/gossip-conflicts - clear gossip cache. do it on both the device at this point of time. restcurl -X DELETE shared/resolver/device-groups/tm-shared-all-big-ips/devices - clear sync cache bigstart restart restjavad -wait 60 seconds to make sure restjavad has had full time to restart restcurl -X POST -d '{}' tm/shared/bigip-failover-state - rediscover/resync devices for gossip 3. Update the lowest generation device storage with the latest generation info. a. Get the Task ID of OIDCDiscoveryTask restcurl -u admin: tm/access/oidc/discover/ | grep selfLink "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/<Task ID>" "selfLink": "https://localhost/mgmt/tm/access/oidc/discover" b. Get current status of this task from rest storage of both active and standby Standby: restcurl /shared/storage?key=tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be { "step": "SLEEP_AND_RUN_AGAIN", "providerName": "/Common/reist-provider", "id": "55feb1ad-52d8-4a83-b0b2-d0981e00c5be", "status": "STARTED", "startTime": "2024-11-13T03:02:43.201+0000", "ownerMachineId": "c601d4c6-5a24-4a94-b46e-c465512cab68", "generation": 2324, "lastUpdateMicros": 1731566304972999, "kind": "tm:access:oidc:discover:oidcdiscovertaskitemstate", "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be" } Active: restcurl /shared/storage?key=tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be { "step": "SLEEP_AND_RUN_AGAIN", "providerName": "/Common/reist-provider", "id": "55feb1ad-52d8-4a83-b0b2-d0981e00c5be", "status": "STARTED", "startTime": "2024-11-13T03:02:43.201+0000", "ownerMachineId": "c601d4c6-5a24-4a94-b46e-c465512cab68", "generation": 14574, "lastUpdateMicros": 1732093908449526, "kind": "tm:access:oidc:discover:oidcdiscovertaskitemstate", "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be" } c. Send a HTTP POST to the out of date device (standby) that includes the output from the up to date device (active) as the post body. restcurl -X POST -u admin: /shared/storage -d '{ "step": "SLEEP_AND_RUN_AGAIN", > "providerName": "/Common/reist-provider", > "id": "55feb1ad-52d8-4a83-b0b2-d0981e00c5be", > "status": "STARTED", > "startTime": "2024-11-13T03:02:43.201+0000", > "ownerMachineId": "c601d4c6-5a24-4a94-b46e-c465512cab68", > "generation": 14574, > "lastUpdateMicros": 1732093908449526, > "kind": "tm:access:oidc:discover:oidcdiscovertaskitemstate", > "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be"}' { "generation": 14573, "lastUpdateMicros": 1732093908449526, "kind": "tm:access:oidc:discover:oidcdiscovertaskitemstate", "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be" } restcurl -u admin: https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be { "step": "SLEEP_AND_RUN_AGAIN", "providerName": "/Common/reist-provider", "id": "55feb1ad-52d8-4a83-b0b2-d0981e00c5be", "status": "STARTED", "startTime": "2024-11-13T03:02:43.201+0000", "ownerMachineId": "c601d4c6-5a24-4a94-b46e-c465512cab68", "generation": 14574, "lastUpdateMicros": 1732093908449526, "kind": "tm:access:oidc:discover:oidcdiscovertaskitemstate", "selfLink": "https://localhost/mgmt/tm/access/oidc/discover/55feb1ad-52d8-4a83-b0b2-d0981e00c5be" } d. The gossip conflict "GENERATION_MISSING" should be resolved and both the active and standby will have the same generation number for OIDCDiscoveryTask.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips