Last Modified: Oct 16, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
21.1.0, 21.1.0.1, 21.1.0.2, 21.1.0.3
Opened: Oct 06, 2026 Severity: 3-Major
After running a full configuration sync, tmsh show cm sync-status continues to report "Changes Pending" even though the sync log shows it completed successfully. Running the same sync command a second time resolves the issue, and the device group then remains "In Sync" normally.
The device group incorrectly shows "Changes Pending" after a configuration sync that actually completed successfully. This can cause automated scripts or monitoring tools that check for "In Sync" status to report a false failure. There is no impact to traffic processing; both devices have matching configurations.
This occurs when all of the following are true: Two or more devices are configured in a High Availability (HA) device group with manual, full-load config sync. A virtual server is deleted and recreated, with its protocol profile changed between TCP and Full-Acceleration (or vice versa). A full configuration sync (force-full-load-push) is run shortly after the change. This has been observed on platforms with ePVA hardware. It has not been reliably reproduced on BIG-IP Virtual Edition.
Run the full configuration sync command a second time. The device group will then show "In Sync" and remain in that state normally, with no further action needed.
None