Bug ID 1381629: Config Sync Issues may arise after UCS restore/save and sync.

Last Modified: Dec 05, 2024

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

Known Affected Versions:
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

Opened: Oct 19, 2023

Severity: 3-Major

Symptoms

Config sync may fail after a UCS save/restore and sync in clustered HA pair. You may see the following errors in the log: - rsync: link_stat "/config/.snapshots_d/customization_group_d/1697724524_:Common:kerberos_auth_config_default_end_deny_ag_1" failed: No such file or directory (2) - rsync error: some files/attrs were not transferred (see previous errors) (code 23) - Caught configuration exception (0), Failed to sync files.. - Remote transaction for device group /Common/GROUPNAME failed with error Caught configuration exception (0), Failed to sync files...

Impact

Config sync fails.

Conditions

1. Should be in a clustered HA pair with auto sync on. 2. Take a UCS and save on both devices in the HA pair. 3. Configure the device with a new kerberos auth config and do a config sync of this configuration. 4. Restore the UCS file saved from before. 5. Run a manual config sync.

Workaround

Remove the customisation group snapshot files and run “tmsh run cm config-sync force-full-load-push to-group GROUPNAME”. This should be run from the device that does not have default kerberos auth config profiles.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips