Bug ID 1008005: Configuration load fails due to BOTDEFENSE_ACTION event in iRule after upgrade

Last Modified: Apr 17, 2024

Affected Product(s):
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, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Opened: Mar 31, 2021

Severity: 3-Major

Symptoms

The configuration fails to load after a software upgrade with an error: err mcpd[6990]: 01071912:3: BOTDEFENSE_ACTION event in rule (/Common/my_irule) requires an associated BOTDEFENSE profile on the virtual-server (/Common/example_virtual_server).

Impact

The configuration load at the end of the upgrade fails.

Conditions

- ASM provisioned - DoS Application profile attached to a virtual server - An iRule with BOTDEFENSE_ACTION event attached to a virtual server - Upgrading from 13.x to 14.x/15.x

Workaround

Prior to upgrade, remove all iRules that have a BOTDEFENSE_ACTION event from all virtual servers. After the upgrade is successful, add the bot-defense profile to the virtual servers and add the iRules.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips