Bug ID 697856: Profile from Common imported to other partition should still point to log-settings in Common

Last Modified: Jan 29, 2019

Bug Tracker

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

Known Affected Versions:
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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4

Fixed In:
14.0.0

Opened: Dec 06, 2017
Severity: 4-Minor

Symptoms

If an access profile exported from the Common partition has log-settings in the Common partition, if the access profile is then imported to another partition, import fails with error that /partition/log-setting-name is not available.

Impact

There are no default log facilities (e.g., default-log-settings) in the partition. You must create them manually.

Conditions

If access profile is exported from Common partition and imported to non-common partition.

Workaround

To work around this issue, use the following procedure: 1. Create log objects with the proper name in the target partition. 2. Import the access profile.

Fix Information

Now all policies exported from Common are expecting log objects to be presented in Common regardless of target partition.

Behavior Change