Bug ID 611482: Local persistence record kept alive after owner persistence record times out (when using pool command in an iRule) .

Last Modified: Dec 21, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7

Fixed In:
13.0.0, 12.1.4, 11.6.3.3

Opened: Aug 17, 2016
Severity: 3-Major
Related AskF5 Article:
K71450348

Symptoms

Local persistence record kept alive after owner persistence record times out (when using pool command in an iRule).

Impact

Discrepancy between persistence records.

Conditions

Universal persistence is configured. A loop of HTTP request is sent to tmm which doesn't own the record. Persistence lookup is performed, but finally the pool command is used for load-balancing pick.

Workaround

Use persist, not pool command, to bind persistence record to a flow.

Fix Information

Fixed keeping alive the owner record.

Behavior Change