Bug ID 479553: Sync may fail after deleting a persistence profile

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.4

Opened: Sep 16, 2014

Severity: 3-Major

Related Article: K22250333

Symptoms

After syncing configuration, the following error occurs: 'One or more persistence attributes are incompatible with the persistence mode for profile'.

Impact

Peer boxes fail to load the configuration.

Conditions

This happens if automatic sync is disabled on a device group and a user both creates and deletes a persistence profile before manually syncing the configuration.

Workaround

There are two possible workarounds: 1. Perform a full sync instead of an incremental sync. 2. Create the profile, then perform a sync, and then delete the profile, and perform a separate sync.

Fix Information

This was an invalid error case being handled internally and was removed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips