Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1821567

Summary: cri-o-1.18 required by AOS4.5 RHEL scaleup is not found
Product: OpenShift Container Platform Reporter: Yang Yang <yanyang>
Component: ReleaseAssignee: Luke Meyer <lmeyer>
Status: CLOSED ERRATA QA Contact: Yang Yang <yanyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, jokerman, miabbott, schoudha
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:25:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yang Yang 2020-04-07 06:01:19 UTC 
Description of problem:

AOS4.5 scaleup installs cri-o-1.18 which does not exist in repo
http://download.eng.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift/4.5/latest/x86_64/os/Packages/

Version-Release number of selected component (if applicable):
4.5 latest

How reproducible:
Always

Steps to Reproduce:
1. RHEL scaleup
2.
3.

Actual results:
TASK [openshift_node : Set fact l_kubernetes_version] **************************
Sunday 05 April 2020  19:23:42 +0800 (0:00:00.596)       0:05:41.934 ********** 
ok: [10.0.32.5] => {"ansible_facts": {"l_kubernetes_version": "1.18"}, "changed": false}
ok: [10.0.32.6] => {"ansible_facts": {"l_kubernetes_version": "1.18"}, "changed": false}

TASK [openshift_node : Override kubernetes version when running CI] ************
Sunday 05 April 2020  19:23:42 +0800 (0:00:00.089)       0:05:42.024 ********** 
skipping: [10.0.32.5] => {"changed": false, "skip_reason": "Conditional result was False"}
skipping: [10.0.32.6] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [openshift_node : Install openshift packages] *****************************
Sunday 05 April 2020  19:23:42 +0800 (0:00:00.082)       0:05:42.106 ********** 
FAILED - RETRYING: Install openshift packages (3 retries left).
FAILED - RETRYING: Install openshift packages (3 retries left).
FAILED - RETRYING: Install openshift packages (2 retries left).
FAILED - RETRYING: Install openshift packages (2 retries left).
FAILED - RETRYING: Install openshift packages (1 retries left).
FAILED - RETRYING: Install openshift packages (1 retries left).
fatal: [10.0.32.6]: FAILED! => {"ansible_job_id": "194782027224.29744", "attempts": 3, "changed": false, "finished": 1, "msg": "No package matching 'cri-o-1.18.*' found available, installed or updated", "rc": 126, "results": ["No package matching 'cri-o-1.18.*' found available, installed or updated"]}
fatal: [10.0.32.5]: FAILED! => {"ansible_job_id": "826009755796.29752", "attempts": 3, "changed": false, "finished": 1, "msg": "No package matching 'cri-o-1.18.*' found available, installed or updated", "rc": 126, "results": ["No package matching 'cri-o-1.18.*' found available, installed or updated"]}

TASK [openshift_node : Package install failure message] ************************
Sunday 05 April 2020  19:26:08 +0800 (0:02:26.403)       0:08:08.510 ********** 
fatal: [10.0.32.5]: FAILED! => {"changed": false, "msg": "Unable to install cri-o-1.18.*, openshift-clients-4.5.*, openshift-hyperkube-4.5.*. Please ensure repos are configured properly to provide these packages and indicated versions.\n"}
fatal: [10.0.32.6]: FAILED! => {"changed": false, "msg": "Unable to install cri-o-1.18.*, openshift-clients-4.5.*, openshift-hyperkube-4.5.*. Please ensure repos are configured properly to provide these packages and indicated versions.\n"}

Expected results:
Scaleup passes without errors

Additional info:
Comment 1 Yang Yang 2020-04-22 07:09:15 UTC 
cri-o-1.18 is available hence move it to verified state.
Comment 3 errata-xmlrpc 2020-07-13 17:25:52 UTC 
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:2409