Bug ID 458822: Cluster status may be incorrect on secondary blades

Last Modified: Mar 17, 2021

Bug Tracker

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

Known Affected Versions:
10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 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, 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

Fixed In:
12.0.0, 11.5.4

Opened: Apr 24, 2014
Severity: 3-Major
Related AskF5 Article:
K16753

Symptoms

Cluster status may be out of date on secondary blades.

Impact

The cluster status when viewed on a secondary blade may not be up to date. clusterd's status will be correct, but mcpd's copy of the message may be out of date.

Conditions

There is a race condition that becomes apparent when the cluster status is changed on the primary. This change may not be affected on the secondary.

Workaround

This is a cosmetic issue.

Fix Information

Changes are now immediately reflected on secondary blades when the cluster status is changed on the primary blade.

Behavior Change