Last Modified: Jun 19, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.6.2
Fixed In:
F5OS-C 1.8.1
Opened: Dec 09, 2024 Severity: 3-Major
If a system controller is rebooted after it's ETCD instance has been started, but before the controller has been fully added to cluster, it can cause a failure that will not automatically recover. The controller will not be able to join the cluster after this failure.
The rebooted controller will persistently fail to join the cluster after this failure. As such the cluster will not be redundant between the 2 system controllers.
A system controller is rebooted after it's local ETCD instance has been started, but before the controller is fully added into the openshift cluster.
Rebuild the openshift cluster to recover the affected system controller.
The fix cleans any stale ETCD state when the process of adding the controller to the cluster after the reboot. This allows the controller to be re-added to the cluster correctly.