Description of problem: When setting up a Rhel worker node by running the openshift_node role within openshift-ansible, the role attempts to install packages that aren't available for all architectures, as such it fails on non-x86_64 architectures. Version-Release number of selected component (if applicable): openshift-ansible release-4.2 How reproducible: Consistent Steps to Reproduce: 1. Against a ppc64le or s390x cluster run the scaleup.yml playbook (following https://access.redhat.com/documentation/en-us/openshift_container_platform/4.1/html/machine_management/adding-rhel-compute) to add an additional Rhel worker node. Actual results: The Install openshift support packages task fails: TASK [openshift_node : Install openshift support packages] ************************************************************ Monday 04 November 2019 10:45:20 -0600 (0:00:00.141) 0:00:40.708 ******* FAILED - RETRYING: Install openshift support packages (3 retries left). FAILED - RETRYING: Install openshift support packages (2 retries left). FAILED - RETRYING: Install openshift support packages (1 retries left). fatal: [192.168.79.50]: FAILED! => {"ansible_job_id": "972667483958.18155", "attempts": 3, "changed": false, "finished": 1, "msg": "No package matching 'microcode_ctl' found available, installed or updated", "rc": 126, "results": ["No package matching 'microcode_ctl' found available, installed or updated"]} PLAY RECAP ************************************************************************************************************ 192.168.79.50 : ok=2 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 Expected results: The task succeeds and required packages are installed. Additional info: A fix has gone into release-4.3 so would only be required for release-4.2.
The referenced pull request is for 4.3. If we want to merge this into 4.2.z, we'll need to create a new ticket that depends on this one, and set this ticket to "target" 4.3 Also, ammcrae, do you have an environment were we can verify this fix? Sounds like what we need to do is to have a 4.3 cluster deployed, and to run the openshift-ansible release-4.3 playbook on a rhel7 node to verify that it doesn't hit package install issues. To verify the 4.2.z ticket when that is created, we'll have to do the same with a cherry-pick pull request branch targeting a 4.2 cluster.
Verified on ppc64le by Manoj Kumar. Verification on s390x in progress.
Verified by Yulia Gaponenko on s390x.
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-2020:0062