Bug ID 574578: failed to load configuration, when cache_cleanup property is defined for AAA AD/LDAP server

Last Modified: Mar 17, 2021

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, 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, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
13.0.0

Opened: Feb 18, 2016
Severity: 3-Major

Symptoms

failure happens when loading configuration and creating AAA AD/LDAP server. cannot load configuration, until AAA AD/LDAP server is modified. the problem is indicated by error log message "Cannot cleanup cache while creating AAA AD Server" The same issue happens during creation of AAA AD/LDAP server if the option cache-cleanup is defined (not 0)

Impact

Unable to start the system

Conditions

cache_cleanup property of AAA AD/LDAP server supposed to be set '0' all the time, except when cache cleanup is requested. if, by any reason, the property is not set to '0' when system starts up, then the system tries to cleanup non existing caches and fails to load configuration.

Workaround

using tmsh, modify object AAA AD/LDAP Server and set cache-cleanup propery to '0' when creating AAA AD/LDAP server, never set cache-cleanup property

Fix Information

when creating an AAA AD/LDAP Server object and cache-cleanup property is specified (other than none), the property is not applied, as there is no cache yet. when modifying an AAA AD/LDAP Server object and cache-cleanup propery is speified along with any other setting, the cache-cleanup property is not applied, but other settings are modified as requested. error log message generated that cache was not cleaned this time.

Behavior Change