Bug ID 883853: Bot Defense Profile with staged signatures prevents signature update

Last Modified: Sep 24, 2020

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5

Fixed In:
16.0.0

Opened: Feb 24, 2020
Severity: 3-Major

Symptoms

When a trying to install a new bot defense signature, the installation fails with the following log message: com.f5.liveupdate.update.dosbotsignatures.file.Update.applyChanges.pl|INFO|Feb 10 13:22:12.924|7347|F5::Dos::BotSignatures::load_from_xml,,Cannot send updated objects to mcp: 01070265:3: The Bot Defense Signature (/Common/Headless Chromium, Chrome) cannot be deleted because it is in use by a Bot Defense Profile Signature Staging.

Impact

The new file cannot be installed.

Conditions

-- A Bot Defense Profile has a staged signature. -- The staged signature points to something that does not exist in the update file.

Workaround

Enforce the staged signature.

Fix Information

Before deleting the signature, the installation process checks to see whether the signature is staged, and if it is, the process unstages it.

Behavior Change