Last Modified: Feb 06, 2026
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4
Opened: Feb 04, 2026 Severity: 3-Major
If a controller is installing Multus and the peer controller is PXE-booted at that time, the multus-config playbook will fail. Logs similar to this will be in /var/log/openshift.log: fatal: [controller-1.chassis.local]: FAILED! => {"msg": "The conditional check 'groups.oo_masters_to_config | length > 1' failed. The error was: error while evaluating conditional (groups.oo_masters_to_config | length > 1): 'dict object' has no attribute 'oo_masters_to_config'\n\nThe error appears to be in '/usr/share/ansible/openshift-ansible/roles/openshift_sanitize_inventory/tasks/main.yml': line 131, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Ensure openshift_master_cluster_hostname is set when deploying multiple masters\n ^ here\n"}
The system is left in a bad state until the cluster is rebuilt.
PXE-booting the standby controller while its peer is installing Multus.
To avoid this, ensure that the Multus installation is completed before PXE-booting the peer controller. To get out of this state, rebuild the OpenShift cluster, as per K000152701.
None