Bug ID 536824: Syncing configuration references to built-in objects in imbalanced device groups causes sync failures

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP All(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, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Jul 30, 2015
Severity: 2-Critical

Symptoms

Creating an APM Access Profile results in sync error similar to the following: 01070734:3: Configuration error: Invalid Devicegroup Reference. The apm_log_config_profile_access (/SO/ap1 /Common/default-log-setting) requires apm_log_config (/Common/default-log-setting) to be syncd to the same devices Creating an Log Publisher results in sync error similar to the following: 01070734:3: Configuration error: Invalid Devicegroup Reference. The log_publisher_destination (/SO/pub1 /Common/local-syslog) requires log_destination_local_syslog (/Common/local-syslog) to be syncd to the same devices

Impact

You are unable to create an Access Profile or Log Publisher that is configured to use built-in objects.

Conditions

The device must be in both a sync-failover device group and a sync-only device group. There must be at least one member in the sync-only group that is not in the sync-failover group. The Access Profile or logging destination must be created in a folder assigned to the sync-only group. For APM Access Profiles, In 12.0.0, merely creating an Access Profile with the default log settings causes the error. In versions prior, explicitly assigning the default-log-setting causes the error. For Log Publishers, assigning a built-in Log Destination (alertd, local-db, local-syslog) causes the error.

Workaround

The best option is to add the missing sync-only devices to the sync-failover device group. Alternatives include creating and only referring to user-created log settings. There is no workaround if the user does not want to add the missing devices to the sync-failover device and must refer to the built-in objects.

Fix Information

Syncing configuration across a Device Service Cluster in this device group setup no longer fails when configuration refers to built-in objects.

Behavior Change