Description of problem: Upgrade nodes failed if ocp containerized deployed with non-ha. PLAY [Verify masters are already upgraded] ********************************************************************************************************************************** TASK [Gathering Facts] ****************************************************************************************************************************************************** ok: [x.x.x.x] TASK [fail] ***************************************************************************************************************************************************************** fatal: [x.x.x.x]: FAILED! => {"changed": false, "failed": true, "msg": "Master running 3.6.173.0.63 must be upgraded to 3.7.0 before node upgrade can be run."} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_nodes.retry ================Debug info When upgrade masters, master has been spitted into master-api and master-controllers. Only IMAGE_VERSION in api&controller service has been set to "v3.7.0" but not master service. And it seems that openshift.common.version came from /etc/sysconfig/atomic-openshift-master. # cat atomic-openshift-master|grep IMAGE IMAGE_VERSION=v3.6.173.0.63 # cat atomic-openshift-master-api|grep IMAGE IMAGE_VERSION=v3.7.0 Version-Release number of the following components: openshift-ansible-3.7.0-0.189.0.git.0.d497c5e.el7.noarch How reproducible: always Steps to Reproduce: 1. Install ocp v3.6(containerized with non-ha deployed) 2. Upgrade masters 3. Upgrade nodes # ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_nodes.yml Actual results: Upgrade nodes failed. Expected results: Upgrade nodes succeed. Additional info: Inventory file and log in attachment.
PR Created: https://github.com/openshift/openshift-ansible/pull/6005
Verified on openshift-ansible-3.7.0-0.196.0.git.0.27cd7ec.el7.noarch
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