Bug ID 474069: ICAP can assert "valid node" on resumption after long-running iRule

Last Modified: Jul 13, 2024

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

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 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

Fixed In:
11.6.0, 11.5.2, 11.4.1 HF6

Opened: Aug 01, 2014

Severity: 3-Major

Related Article: K16072

Symptoms

If the IVS connection is closed while ICAP is processing an iRule that completes asynchronously, and if on resumption of procesing the ICAP response an abort occurs, the closing is still processed after the abort, resulting in an assertion "valid node" and a TMM crash.

Impact

TMM crash

Conditions

Long-running iRule on an ICAP event. IVS connection is closed during iRule processing. ICAP server response causes abort (such as protocol error).

Workaround

If possible, avoid commands that could complete asynchronously (like session table) in ICAP iRule events.

Fix Information

If the IVS connection is closed while ICAP is processing an iRule that completes asynchronously, and if on resumption of processioning the ICAP response an abort occurs, the closing is not processed after the abort, and no crash occurs.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips