Bug ID 932213: Local user db not synced to standby device when it is comes online after forced offline state

Last Modified: Sep 13, 2023

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

Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2

Fixed In:
16.1.0, 15.1.4.1, 14.1.4.5

Opened: Jul 29, 2020

Severity: 3-Major

Symptoms

Local user db is not synced to the standby device when it comes online after being forced offline.

Impact

The newly created user is not synced to the standby device unless localdbmgr is restarted on the standby.

Conditions

Valid high availability (HA) configuration. - Make the standby device forced offline - create a new local db user in the online device - bring back the standby device online.

Workaround

None

Fix Information

Fixed the issue by handling the forced offline scenario.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips