Bug ID 1474157: Inserting a new BX520 blade caused existing blade to be removed from the show cluster output.

Last Modified: Jun 19, 2025

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

Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1

Opened: Jan 05, 2024

Severity: 2-Critical

Symptoms

A new double width blade was inserted into slot 7 of a 32 slot chassis, and the blade in slot 9 was remove from the show cluster output populated by orchestration-manager. blade-9 was still in the openshift cluster and still functioning correctly, but was not being reported in show cluster.

Impact

Blade-9 status was not visible in the show cluster output

Conditions

Issue was non reproducible, but the original conditions were that the blade in slot 7 was RMA'd and when the replacement blade was inserted, the blade in slot 9 was removed from the show cluster output.

Workaround

Restart orchestration-manager to re-read the blade population from the active system controller: systemctl restart orchestration_manger_container.service

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips