Bug ID 1754769: The third Openshift ETCD instance may not start up after a power cycle

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: Nov 23, 2024

Severity: 2-Critical

Symptoms

Upon running the 'show cluster' command on the controller CLI, you will observe that the etcd-ha-running field is marked as false.

Impact

You will not see any effect on tenants.

Conditions

After a chassis power cycle followed by a contoller failover, the third Openshift ETCD instance may fail to start. This is caused by a lock in the underlying database.

Workaround

You can initiate a controller failover

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips