Description of problem: Trigger upgrade against atomic hosts ha, upgrade failed at task [Create the ha systemd unit files]. failed: [x.x.x.x] (item=api) => { "failed": true, "item": "api" } MSG: AnsibleUndefinedVariable: 'l_bind_docker_reg_auth' is undefined failed: [qe-jliu-con1-master-etcd-1.0922-8gh.qe.rhcloud.com] (item=controllers) => { "failed": true, "item": "controllers" } MSG: AnsibleUndefinedVariable: 'l_bind_docker_reg_auth' is undefined to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.retry Version-Release number of the following components: atomic-openshift-utils-3.7.0-0.127.0.git.0.b9941e4.el7.noarch How reproducible: always Steps to Reproduce: 1. Install HA env on atomic hosts. 2. Trigger upgrade # ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.yml -v|tee log 3. Actual results: Upgrade failed. Expected results: Upgrade succeed. Additional info: Please attach logs from ansible-playbook with the -vvv flag
PR Created: https://github.com/openshift/openshift-ansible/pull/5502 After merging, backport PR will be created for 3.6, 1.5, 1.4
Remove testblocker, this bug has been fixed based on openshift-ansible-3.7.0-0.133.0.git.0.06c6bc7.el7.noarch. @scott You can modify the bug status.
All backports merged: 3.6: https://github.com/openshift/openshift-ansible/pull/5521 1.5: https://github.com/openshift/openshift-ansible/pull/5522 1.4: https://github.com/openshift/openshift-ansible/pull/5523
Version: ansible-2.3.2.0-2.el7.noarch openshift-ansible-3.7.0-0.144.2.git.0.da1dd6c.el7.noarch Upgrade succeed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188
This was fixed in 3.7 in the referenced errata. It has not been fixed in 3.4. This bug should not be re-opened, it should be cloned for 3.4.