Bug ID 696808: Disabling a single pool member removes all GTM persistence records

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP DNS, GTM(all modules)

Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3

Fixed In:
14.0.0, 13.1.0.4, 12.1.3.4

Opened: Nov 30, 2017
Severity: 3-Major
Related AskF5 Article:
K35353213

Symptoms

Disabling a single pool member removes all GTM persistence records.

Impact

All GTM persistence records are accidently cleared.

Conditions

1. WideIP with persistence enabled. 2. drain-persistent-requests no. 3. GTM pool member toggled from enabled to disabled.

Workaround

Set drain-persistent-requests yes.

Fix Information

When drain-persistent-requests is set to no, only the persistence records associated with the affected pool members are cleared when a resource is disabled.

Behavior Change