Bug ID 508699: Import with reuse is failing if profile and resource are sharing the same name

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2

Fixed In:
12.0.0, 11.6.2

Opened: Feb 23, 2015
Severity: 3-Major
Related Article:
K03737485

Symptoms

If a profile and a resource have the same name, and there is attempt to export and re-import it using the 'Reuse Existing Objects' option, import fails with an error.

Impact

Import does not work. This represents minimal impact, however, because failure occurs only in the reuse-objects case.

Conditions

Profile and resource share the same name, for example: access-profile /Common/google and resource-assign /Common/google. Export and import using the 'Reuse Existing Objects' option.

Workaround

A. Use profile copy instead of import with reuse. B. Perform the following steps: 1) Unpack .conf.tar.gz. 2) Open .conf. 3) Change name of resource and all links to it from /@partition/@name to a unique name, such as @name-123. 4) Repack .conf.tar.gz.

Fix Information

Import with 'Reuse Existing Objects' now succeeds when profile and resource share the same name.

Behavior Change