Description of problem: Run upgrade_control_plane.yml to upgrade masters only against a ha rpm installed env, upgrade failed for "No package matching 'atomic-openshift-3.7.0' found available, installed or updated" in node hosts, which should not be ran. TASK [openshift_version : Install the base package for versioning] ************* skipping: [qe-jliu-ha-lb-1.0925-pt5.qe.rhcloud.com] => { "changed": false, "skip_reason": "Conditional result was False", "skipped": true } fatal: [qe-node-1.x.x.x]: FAILED! => { "changed": false, "failed": true, "rc": 126, "results": [ "No package matching 'atomic-openshift-3.7.0' found available, installed or updated" ] } MSG: No package matching 'atomic-openshift-3.7.0' found available, installed or updated fatal: [qe-node-2.x.x.x]: FAILED! => { "changed": false, "failed": true, "rc": 126, "results": [ "No package matching 'atomic-openshift-3.7.0' found available, installed or updated" ] } MSG: No package matching 'atomic-openshift-3.7.0' found available, installed or updated <--snip-> Version-Release number of the following components: ansible-2.3.2.0-2.el7.noarch openshift-ansible-3.7.0-0.127.0.git.0.b9941e4.el7.noarch How reproducible: always Steps to Reproduce: 1. Install ocp 3.6 2. Upgrade masters ansible-playbook -i hosts $/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml 3. Actual results: Upgrade failed as installer tried to install packages on nodes. Expected results: Upgrade masters succeed with no changes on dedicated nodes. Additional info: Please attach logs from ansible-playbook with the -vvv flag
Thought this was fixed in https://github.com/openshift/openshift-ansible/pull/5380 but maybe that was slightly different
PR Created: https://github.com/openshift/openshift-ansible/pull/5632
PR Merged.
Version: openshift-ansible-3.7.0-0.150.0.git.0.15c09f1.el7.noarch 1. Install ocp 3.6 2. Upgrade masters ansible-playbook -i hosts $/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade_control_plane.yml Upgrade masters succeed with no changes on dedicated nodes.
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