Bug ID 423482: Removing the gateway failsafe pool in web interface does not set the pool::gateway failsafe device property to none

Last Modified: Mar 12, 2019

Bug Tracker

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

Known Affected Versions:
10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Jun 18, 2013
Severity: 3-Major
Related AskF5 Article:
K14787

Symptoms

Removing the gateway failsafe pool in the web interface does not set the pool::gateway failsafe device property to none.

Impact

Creates confusion about the current pool::gateway failsafe device configuration.

Conditions

When the gateway failsafe pool is removed from web user interface, the pool maintains the prior gateway failsafe device. This is seen on listing the pool in tmsh.

Workaround

The pool::gateway failsafe device property can be set to none using tmsh.

Fix Information

Removing the gateway failsafe pool in web interface now correctly sets the pool::gateway failsafe device property.

Behavior Change