Description of problem: I have a 4.2 cluster deployed on UPI/baremetal. 2 of the workers are RHEL7. Following doc to do minor upgrade of OpenShift 4.2.0 to 4.2.2 is failing for me. Doc referencing: https://docs.openshift.com/container-platform/4.2/updating/updating-cluster-rhel-compute.html Error message from output of openshift-ansible playbook launch: fatal: [worker3.openshift4.vco.lab]: FAILED! => {"ansible_job_id": "98433931110.174592", "attempts": 3, "changed": false, "finished": 1, "msg": "No package matching 'openshift-clients-4.2.2' foun d available, installed or updated", "rc": 126, "results": ["All packages providing cri-o are up to date", "No package matching 'openshift-clients-4.2.2' found available, installed or updated"]} Version-Release number of the following components: rpm -q openshift-ansible openshift-ansible-4.2.1-201910220950.git.190.b6097b1.el7.noarch rpm -q ansible ansible-2.8.6-1.el7ae.noarch ansible --version ansible 2.8.6 config file = /usr/share/ansible/openshift-ansible/ansible.cfg configured module search path = [u'/home/dcain/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] How reproducible: Steps to Reproduce: 1. cd /usr/share/ansible/openshift-ansible 2. ansible-playbook -i ~/ansible/hosts playbooks/upgrade.yml 3. Failure message observed Actual results: TASK [openshift_node : Package install failure message] ******************************************************************************************************************************************* Saturday 02 November 2019 09:44:08 -0400 (0:02:16.774) 0:11:30.209 ***** fatal: [worker3.openshift4.vco.lab]: FAILED! => {"changed": false, "msg": "Unable to install cri-o, openshift-clients-4.2.2, openshift-hyperkube-4.2.2. Please ensure repos are configured properly to provide these packages and indicated versions.\n"} Expected results: Nodes upgrade both openshift-clients and openshift-hypercube on RHEL7 worker nodes. Additional info: Seeing actual yum packages available to be installed on RHEL7 worker nodes are clients=4.2.1-201910220950.git.1.4fb8512.el7 and hyperkube=4.2.1-201910220950.git.0.7e13ab9.el7. Does this mean we don't have packages yet for upgrading RHEL7 workers?
Seem like the same root cause like 1766830.
Proposed: https://github.com/openshift/openshift-ansible/pull/11997
Due to a release issue, the images were rebuilt to 4.2.2 however the content for the RPMs was the same and were not rebuilt. This was an exception to the process. However .z versioning will be dropped from RPMs and images in the future so relaxing version requirements will be necessary.
Verified it with 4.2.0-0.nightly-2019-11-11-233305 TASK [openshift_node : Install openshift packages] ***************************** Tuesday 12 November 2019 21:55:52 +0800 (0:00:00.059) 0:04:48.909 ****** ok: [xxxxx.openshift.com] => {"ansible_job_id": "968293069808.117710", "attempts": 1, "changed": false, "changes": {"installed": [], "updated": []}, "finished": 1, "msg": "", "obsoletes": {"python-urllib3": {"dist": "noarch", "repo": "@anaconda/7.7", "version": "1.10.2-7.el7"}}, "rc": 0, "results": ["All packages providing cri-o are up to date", "All packages providing openshift-clients-4.2* are up to date", "All packages providing openshift-hyperkube-4.2* are up to date", ""]}
This bug also affects adding RHEL7 worker nodes to an OCP 4.2.2 cluster.
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/RHBA-2019:3869