Bug ID 554324: Signatures cannot be updated after Signature Systems have become corrupted in database

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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

Fixed In:
12.1.0, 11.6.1 HF1

Opened: Oct 26, 2015

Severity: 3-Major

Related Article: K32359424

Symptoms

Signatures cannot be updated after signature systems have become corrupted in the configuration database.

Impact

Signatures cannot be updated.

Conditions

Signature systems are corrupted in configuration database. This can occur after upgrading to v11.6.0, v11.6.1, or v12.0.0.

Workaround

Delete signature systems with an ID greater than 38, and re-add them by performing a signature update. You can delete these signature systems by running the following command: mysql -u root -p$(perl -MPassCrypt -nle 'print PassCrypt::decrypt_password($_)' /var/db/mysqlpw) -e "DELETE FROM PLC.NEGSIG_SYSTEMS WHERE system_group = ''"

Fix Information

Signature System data corruption is corrected upon upgrade, and Signatures can be subsequently upgraded.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips