Bug ID 1026277: Apply Policy can get ignored in auto-sync setup, while importing/replacing several existing policies with policies that have Policy Builder enabled

Last Modified: Apr 17, 2024

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

Known Affected Versions:
14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,

Fixed In:
17.0.0, 16.1.4

Opened: Jun 16, 2021

Severity: 4-Minor


With auto-sync enabled, replacing multiple policies on Unit-A with policies having Policy Builder enabled, "Apply Policy" initiated by Policy Builder can be ignored at Unit-B that results all the policy on Unit-A appear as not-edited while a few policies on Unit-B appear as edited.


Inconsistent policy state in auto-sync members


-- Using auto-sync -- Multiple policies are replaced (imported as replacing method) at the same time Note : bulk import/replace is only possible via Ansible (also, maybe scripting that utilizes REST API) -- Those imported policies have Policy Builder enabled


Make a minor update on those affected policies, then "Apply Policy" will fix the inconsistent state.

Fix Information

The particular call is now not relayed to the peer

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips