Bug ID 1102765: Blade is not in the Ready status in the cluster

Last Modified: May 29, 2024

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

Fixed In:
F5OS-C 1.6.0

Opened: Apr 26, 2022

Severity: 3-Major


Blade does not join the cluster. [root@controller-2 ~]# oc get nodes NAME STATUS ROLES AGE VERSION blade-1.chassis.local NotReady compute 3h v1.11.0+d4cacc0 blade-2.chassis.local Ready compute 3h v1.11.0+d4cacc0 controller-1.chassis.local Ready infra,master 3h v1.11.0+d4cacc0 controller-2.chassis.local Ready infra,master 3h v1.11.0+d4cacc0 service failure messages on the blade console May 11 00:11:28 blade-2.chassis.local platform-deployment[13130]: Job for var-mnt-chassis.mount failed. See "systemctl status var-mnt-chassis.mount" and "journalctl -xe" for details.


The blade cannot join the cluster and cannot run any tenant.


It happens intermittently and rarely on up/downgrade.


Reboot the blade through the chassis partition CondfD. CLI command: cluster nodes node blade-X reboot Where X is the slot number of the blade to reboot.

Fix Information

When the symptom is detected, the monitoring script resets the blade NIC driver.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips