Bug ID 1590425: Adding blade to openshift cluster can fail with ansible error

Last Modified: Mar 04, 2026

Affected Product(s):
F5OS F5OS-C, Install/Upgrade(all modules)

Known Affected Versions:
F5OS-C 1.6.2, F5OS-C 1.6.4

Fixed In:
F5OS-C 1.8.0

Opened: May 29, 2024

Severity: 3-Major

Symptoms

Adding or re-Adding a blade to the OpenShift cluster can fail with the following ansible error: fatal: [blade-2.chassis.local -> controller-1.chassis.local]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: {{ hostvars[groups.oo_first_master.0].openshift.master.api_url }}: 'dict object' has no attribute 'master'\n\nThe error appears to be in '/usr/share/ansible/openshift-ansible/roles/openshift_manage_node/tasks/main.yml': line 5, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n# systemd to start the master again\n- name: Wait for master API to become available before proceeding\n ^ here\n"} ID1590425 can affect controllers too: Controller-1 Was showing missing from # show system redundancy-details LOCAL LOCAL PEER PEER CONTROLLER ACTIVE LOCAL ACTIVE ACTIVE PEER ACTIVE NUMBER DESIRED HEALTHY GRANTED DESIRED HEALTHY GRANTED ------------------------------------------------------------------ 2 true true true false true false If you observe below logs from openshift.log, it indicates the ansible openshift.fact appears to get corrupted/missing 2025-04-30 12:14:05.303144 - changed: [controller-1.chassis.local] => (item=/etc/ansible/facts.d/openshift.fact) => {"ansible_loop_var": "item", "changed": true, "item": "/etc/ansible/facts.d/openshift.fact", "path": "/etc/ansible/facts.d/openshift.fact", "state": "absent"} 2025-04-30 15:15:52.157907 - changed: [controller-1.chassis.local] => (item=/etc/ansible/facts.d/openshift.fact) => {"ansible_loop_var": "item", "changed": true, "item": "/etc/ansible/facts.d/openshift.fact", "path": "/etc/ansible/facts.d/openshift.fact", "state": "absent"} 2025-04-30 16:40:38.152758 - changed: [controller-1.chassis.local] => (item=/etc/ansible/facts.d/openshift.fact) => {"ansible_loop_var": "item", "changed": true, "item": "/etc/ansible/facts.d/openshift.fact", "path": "/etc/ansible/facts.d/openshift.fact", "state": "absent"}

Impact

New blade/controller will not join the cluster correctly.

Conditions

Adding or re-Adding a blade to blade the OpenShift cluster after the etcd instance been rebuilt.

Workaround

Rebuild the OpenShift cluster. Rebuilding will regenerate the corrupted openshift.fact file.

Fix Information

The fix checks the openshift.fact file before running any ansible playbooks to make sure it is correct.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips