Bug ID 961065: Reuse Existing Objects behavior change

Last Modified: Jul 21, 2021

Bug Tracker

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

Known Affected Versions:
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

Opened: Oct 30, 2020
Severity: 3-Major

Symptoms

When importing an Access policy in version 15.1.x with the option "Reuse Existing Objects", if the object does not exist, then a new object is created with name format <new Policy Name>-<Existing Object Name in exported access policy> instead of being created with the same name as the object name in the exported access profile. This is different behavior from previous BIG-IP releases.

Impact

Reuse Existing Objects setting may add redundant config objects when importing a large number of policies which share the same objects on the source device.

Conditions

"Reuse existing objects " option is used during access policy import

Workaround

-) Extract the export -) Run the following sed script on ng-export.conf # sed -i -e 's/\/\@name-/\//g' ng-export.conf -) Recreate the export tarball.

Fix Information

None

Behavior Change