Bug ID 1591069: Blades may fail to get marked as InCluster in "show cluster" output after rolling upgrade

Last Modified: Jan 30, 2025

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.8.0

Opened: May 31, 2024

Severity: 3-Major

Symptoms

After a rolling upgrade, one or more blades may be marked as "Not In Cluster" in the "show cluster" output.

Impact

System will function correctly, but "show cluster" output will show the blade is not being marked "In Cluster".

Conditions

Perform rolling upgrades from a manufacturing-installed F5OS C v1.7.0 to F5OS C v1.7.1.

Workaround

To workaround the issue, the orchestration-manager daemon can be restarted, which will result in the "In Cluster" status being updated. This action needs to be performed from the shell on both controllers. systemctl restart orchestration_manager_container.service

Fix Information

Fixed issue in the orchestration-manager daemon causing the "In Cluster" status not being updated.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips