Bug ID 2196293: The file /var/omd/CLUSTER_REINSTALL on Standby causes openshift reinstall after failover

Last Modified: Jan 16, 2026

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

Known Affected Versions:
F5OS-C 1.5.0, F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2

Opened: Dec 26, 2025

Severity: 3-Major

Symptoms

If /var/omd/CLUSTER_REINSTALL exists on Standby, when there is a controller failover, an openshift reinstall triggers.

Impact

Service outage of Chassis

Conditions

- /var/omd/CLUSTER_REINSTALL exists on the Standby controller. - A failover to that controller occurs.

Workaround

The file /var/omd/CLUSTER_REINSTALL is created by the user in order to trigger an openshift reinstall. It should not normally exist. Proactively check that /var/omd/CLUSTER_REINSTALL does not exist on the Standby controller. For example, from Active blade console: [root@controller-A(VELOS):Active ~]# ssh controller-B ls -la /var/omd/CLUSTER_REINSTALL ls: cannot access /var/omd/CLUSTER_REINSTALL: No such file or directory Where "controller-B" is the other controller, for example "controller-2".

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips