Bug ID 597291: Upgrade and subsequent config sync fails if there is an ASM policy with empty name.

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP ASM, Install/Upgrade(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Jun 03, 2016

Severity: 3-Major

Related Article: K59135544


After upgrading, to 12.0.0 or higher ASM shows as not ready in the GUI. /var/log/ltm has this signature: err asm_tables_dump.pl[20647]: gave up waiting for ASM to start, please try again later.


System upgrades, but ASM reports as not ready and config sync fails.


This occurs on upgrading, when one or more ASM policies contains no name. It is not known what causes an ASM policy to have no name.


If you cannot find the policy in the GUI with no name, the following mysql command can help with detection: mysql -uroot -p`perl -MF5::DbUtils -e 'print F5::DbUtils::get_mysql_password(user => qw{root})'` -e 'SELECT * FROM PLC.PL_POLICIES WHERE name = ""\G' The policy can be removed from the GUI, and at that point restarting the system should succeed as expected.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips