Bug ID 648008: bd keeps coring after upgrade to 12.1.2 or later

Last Modified: Dec 20, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, Install/Upgrade(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Feb 28, 2017
Severity: 3-Major
Related AskF5 Article:
K70289415

Symptoms

Pre-existing traffic data files from a previous attempt to perform a roll-forward/upgrade remain on the disk under /var/asmdata1/traffic_data, even after you set ucs.asm.traffic_data.save to disable. The qkview contains errors such as the following. -- ASM subsystem error (asm_start,F5::DbUpgrade::__ANON__): DBD::mysql::db do failed: Too many partitions (including subpartitions) were defined --

Impact

The ASM enforcer application continually fails, causing unit instability.

Conditions

This can occur after upgrading ASM to 12.1.2 or later, and rolling forward the configuration.

Workaround

Upgrade by saving a UCS on 12.1.0, performing a clean install of 12.1.2, and then loading the UCS onto 12.1.2 (or later). In the manual save/load UCS process, the upgrade of the Request Log can be disabled, which works around the error, so the UCS can load without error. This can be set by: # tmsh modify sys db ucs.asm.traffic_data.load value never

Fix Information

/var/asmdata1/traffic_data is now cleared as part of UCS load cleanup, so the issue no longer occurs.

Behavior Change