Bug ID 1575585: Unable to add blade to Openshift cluster if newly-installed blade is not member of active partition

Last Modified: Jan 30, 2025

Affected Product(s):
F5OS F5OS, F5OS-C, Velos(all modules)

Known Affected Versions:
F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2

Fixed In:
F5OS-C 1.8.0

Opened: Apr 03, 2024

Severity: 3-Major

Symptoms

After a blade is clean-installed (PXE, USB, etc), if the blade is not a member of an enabled/functioning partition, the system is unable to add it to the Openshift cluster successfully. If an administrator attempts to log into the blade via SSH, it will prompt them that root's password is expired and needs to be changed: [root@controller-1(VELOS) ~]# ssh blade-1 You are required to change your password immediately (root enforced) Changing password for root. (current) UNIX password: Connection to blade-1 closed. [root@controller-1(VELOS) ~]# The "show cluster" command output will report that a blade is reachable ("able to ping"), but will not be able to connect to it ("able to SSH"): ABLE ABLE IN READY TO TO PARTITION INDEX NAME INSERTED CLUSTER CLUSTER PING SSH STATE LABEL -------------------------------------------------------------------------------------------------- 1 blade-1.chassis.local true false false true false Not In Cluster 2 blade-2.chassis.local true false false true false Not In Cluster 3 blade-3.chassis.local true false false true false Not In Cluster

Impact

- Blade will not join Openshift cluster.

Conditions

-- Blade is not a member of a VELOS partition, or is a member of a disabled partition. -- A clean install is performed on blade (i.e. PXE install); this will be the case during an RMA replacement.

Workaround

Either configure the blade to be a member of an enabled partition, or manually log into the blade as root and go through the "change password" process.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips