Bug ID 599221: ASM Policy cannot be created in non-default partition via the Import Policy Task

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1

Fixed In:
13.0.0, 12.1.3.2

Opened: Jun 14, 2016
Severity: 2-Critical

Symptoms

An ASM Policy cannot be created in a non-default (/Common) partition using the Import Policy Task (/mgmt/tm/asm/tasks/import-policy).

Impact

Policy is created in /Common instead of the specified partition.

Conditions

User attempts to create a new ASM policy in a non-/Common partition using a file or template via the import policy tasks.

Workaround

1) Create a Policy in the desired partition via a POST to the /mgmt/tm/asm/policies endpoint. 2) Execute the Import Policy Task (/mgmt/tm/asm/tasks/import-policy) using the created policy as the policyReference to overwrite it.

Fix Information

Policy Import creates new policies in the specified partition.

Behavior Change