Bug ID 772165: Sync Failed due to Bot Defense profile not found.

Last Modified: Jul 20, 2024

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 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, 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, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Fixed In:
15.0.0, 14.1.2.7

Opened: Apr 12, 2019

Severity: 3-Major

Symptoms

A sync failure might happen in a sync-failover device group after manually editing the /config/bigip.conf file and removing the Bot Defense profiles, and then performing a config sync. The system reports a sync error message similar to this: FODG (Sync Failed): A validation error occurred while syncing to a remote device. - Sync error on device-b: Load failed from /Common/device-a 01020036:3: The requested profile (/Common/bot-defense-device-id-generate-before-access) was not found. - Recommended action: Review the error message and determine corrective action on the device.

Impact

Sync failure.

Conditions

Manually editing the /config/bigip.conf file and removing the Bot Defense profile, then loading the config, and performing a config sync. This sync failure may happen even without ASM provisioned, and in rare cases may happen even if you have not modified the base Bot Defense profile.

Workaround

Reload the config from the receiving device, and then perform a force sync in the opposite direction, overriding the previous changes. This should bring the system back to in sync.

Fix Information

Sync failures no longer happen when removing Bot Defense profiles from the config file and loading config.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips