Bug ID 771545: Export access policy does not include apm log-setting config

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP APM(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, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0

Opened: Apr 10, 2019

Severity: 4-Minor

Symptoms

If there is an access policy that uses APM log-settings, the BIG-IP system does not export that log-setting configuration when exporting the access policy. Later when you try to import this access policy into a different BIG-IP system that does not have the corresponding log-settings, import fails. The following error occurs when attempting to import: # ng_import --logfile profile_Common_simple-ap-01.conf.tar.gz simple-ap-01 Import error: 01070734:3: Configuration error: Log settings /Common/debug-log-settings associated with profile /Common/simple-ap-01 does not exist. Unexpected Error: Loading configuration process failed.

Impact

Import fails and reports an error.

Conditions

When importing the access policy into an APM configuration that does not have corresponding log-settings.

Workaround

Create an APM log-setting configuration with the same name using: tmsh create apm log-setting debug-log-settings

Fix Information

A Warning Banner has been added to create objects referenced by access profile before import.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips