Bug ID 647834: Failover DB variables do not correctly implement 'reset-to-default'

Last Modified: Sep 13, 2023

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

Known Affected Versions:
10.2.4, 11.2.1, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Feb 27, 2017

Severity: 3-Major

Symptoms

When the 'modify sys db' command option 'reset-to-default' is issued, the new value does not take effect, even though 'list sys db' displays the desired value.

Impact

The configuration change does not take effect.

Conditions

This is known to affect at least the following failover-related DB variables: log.failover.level failover.nettimeoutsec failover.debug failover.usetty01 failover.rebootviasod failover.packetcheck failover.packetchecklog failover.secure mysqlhad.heartbeattimeout mysqlhad.debug mysqldfailure.enabled mysqldfailure.haaction.primary mysqldfailure.haaction.secondary

Workaround

Explicitly set the DB variable to the desired value.

Fix Information

reset-to-default restores the default values.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips