Bug ID 479543: Transaction will fail when deleting pool member and related node

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(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, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.1 HF1, 11.5.4, 11.4.1 HF9

Opened: Sep 16, 2014

Severity: 3-Major

Related Article: K15949

Symptoms

Removing a pool and the related nodes in the same transaction will fail. It will output an error message similar to the following: 01070110:3: Node address '/Common/12.33.22.2' is referenced by a member of pool '/Common/mypool'.

Impact

A pool and related nodes cannot be deleted within the same transaction.

Conditions

Create a pool, add a single pool member (which creates the associated node). If you then delete the pool and node in the same transaction, the transaction will fail.

Workaround

If you delete the pool and nodes in 2 separate transactions, the process will succeed.

Fix Information

The pool-member reference check for the node was moved to a later stage of validation, allowing the pool and pool members to be updated/deleted. This ensures that when the delete code for the node checks for references from a pool, there will be none.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips