Last Modified: Feb 20, 2026
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Jan 23, 2026 Severity: 3-Major
After a controller is freshly-installed and Openshift is installed on it, that controller will be unable to launch the third etcd instance due to errors in the /etc/etcd/etcd-3.conf configuration file. If this controller becomes active, this may result in the Openshift cluster becoming unresponsive and unhealthy. /var/log/openshift.log will be logging repeating error messages such as the following: displayClusterStatus: skip display since the last query nodes failed queryNodes: oc get nodes command failed - Do not parse output file Controller 1 is inserted, pingable, sshable, InCluster, and cluster is initialized and 3rd etcd was installed Controller 2 is inserted, pingable, sshable, InCluster, and cluster is initialized and 3rd etcd was installed ETCD: No controllers are currently active - reset delay in launch of the third etcd docker container
Openshift cluster unhealthy. Unable to manage tenants.
- VELOS system controller - Freshly installed (i.e. via USB install or PXE install) - non-default internal chassis network range (something other than RFC6598)
On the newly-installed controller, edit /etc/etcd/etcd-3.conf and modify the references to "100.65." to the correct internal chassis network prefix. See /etc/etcd/etcd.conf. This can be done automatically by running the following commands in a bash shell on the controller. (source /etc/sysconfig/chassis_network_active.txt && [ -n "${network_prefix:-}" ] && sed -i.ID2216701.backup -e "s,100\.65\.,${network_prefix}.,g" /etc/etcd/etcd-3.conf )
None