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: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
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, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3

Fixed In:
17.0.0

Opened: Jun 16, 2021
Severity: 4-Minor

Symptoms

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.

Impact

Inconsistent policy state in auto-sync members

Conditions

-- 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

Workaround

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