Bug ID 425412: Cluster sync fails endlessly when account (httpclass) is deleted.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.3.0, 11.4.0

Fixed In:
11.5.0

Opened: Jul 17, 2013
Severity: 3-Major
Related AskF5 Article:
K32850114

Symptoms

Cluster sync fails endlessly if an account has been deleted. This occurs when ASM is disabled for an HTTP Class, or the HTTP Class is deleted.

Impact

Apply sync on a new blade will get stuck.

Conditions

This may be more likely to happen if a new blade is added while the policy sync files are still in the sync file directory (/var/ts/var/cluster/send/). DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`DCC`.`CLUSTER_SYNC_FILES`, CONSTRAINT `CLUSTER_SYNC_FILES_ibfk_1` FOREIGN KEY (`account_id`) REFERENCES `ACCOUNTS` (`account_id`) ON DELETE CASCADE) at /usr/lib/perl5/site_perl/F5/Cluster/Sync.pm line 703. ----------------------------------------------------------------------

Workaround

Delete the files under /var/ts/var/cluster/send on all blades.

Fix Information

Cluster synchronization no longer fails if an account has been deleted. This used to occur when ASM is disabled for an HTTP Class, or the HTTP Class is deleted.

Behavior Change