Bug ID 625114: Internal sync-change conflict after update to local users table

Last Modified: May 10, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5

Fixed In:
13.0.0, 12.1.3.6

Opened: Oct 26, 2016
Severity: 2-Critical
Related AskF5 Article:
K08062851

Symptoms

User sync is initiated unexpectedly and automatically by the REST framework. To the internal sync system, this will appear as if the same change is being made manually on all devices, causing a change conflict. In other words, 'show cm sync-status' will return output similar to the following: ------------------------------------------------------------------------------------------------- CM::Sync Status ------------------------------------------------------------------------------------------------- Color red Status Changes Pending Mode high-availability Summary There is a possible change conflict between device1 and device2. Details device1: connected mydg (Changes Pending): There is a possible change conflict between device1 and device2. - Recommended action: Synchronize device2 to group mydg In addition, users that were synchronized by the REST framework may not have the correct role and/or partition assigned to them.

Impact

An unexpected change conflict between your devices. In some cases, high CPU utilization by restjavad may be observed.

Conditions

A sync-failover device group exists. In addition, the REST framework's 'gossip' mechanism must be set up correctly. This should happen automatically, but might not be ready yet. You can confirm that this is the case by running 'restcurl shared/resolver/device-groups/tm-shared-all-BIG-IPs/devices'. The output must show all your devices, and show that they all have the same 'version' and the same 'restFrameworkVersion'.

Workaround

When you have the change conflict, force a sync to the device group from the device where the user was originally created. The high CPU utilization by restjavad may persisting after a full sync. Recommendation is to restart the restjavad service: restart sys service restjavad

Fix Information

Internal sync-change conflict is no longer present after update to local users table.

Behavior Change