Bug ID 2161025: Long-running bulk transactions can block the control plane

Last Modified: Dec 17, 2025

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3

Opened: Nov 23, 2025

Severity: 3-Major

Symptoms

Some actions, such as Set Active, or config calls that cause internal Set Active actions, take the global DB lock until the action is finished. When multiple heavy actions like this are called together within one Bulk Task, the DB lock is taken and held for potentially a very long time.

Impact

System processes may wait for a lock for a long time causing system congestion which may impact various actions such as other Apply Policy commands, periodic file cleanup, and configuration synchronization.

Conditions

A bulk task is created with multiple commands to add/modify/delete signatures or signature sets that are attached to policies.

Workaround

Do not issue a series of long running actions as a single Bulk Task.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips