Bug ID 613728: Import/Activate Security policy with 'Replace policy associated with virtual server' option fails

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0, 13.1.3, 12.1.4

Opened: Aug 31, 2016

Severity: 4-Minor

Symptoms

Visible errors in the BIG-IP Configuration utility: -- MCP Validation error - 01071abb:3: Cannot create/modify published policy '/Common/<ltm_policy_name>' directly, try specifying a draft folder like '/Common/Drafts/<ltm_policy_name>'. -- MCP Validation error - 01071726:3: Cannot deactivate policy action '/Common/<asm_policy_name>'. It is in use by ltm policy '/Common/<asm_policy_name>'.

Impact

Security Policy is activated but not assigned to the LTM policy.

Conditions

-- ASM provisioned. -- Having an active Security policy 'A' assigned to an LTM L7 Policy 'L'. -- Import/Activate Security policy 'B' with the option 'Replace policy associated with virtual server' enabled, to replace security policy 'A'.

Workaround

Run the following command prior to the Import/Activate of a Security policy action: --------- # tmsh modify ltm policy L legacy ---------

Fix Information

The process of importing/activating a Security policy now correctly replaces an existing policy, when the option 'Replace policy associated with virtual server' is enabled.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips