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

Bug 1876724

Summary: RHCOS nodes' cri-o version is not consistent with RHEL
Product: OpenShift Container Platform Reporter: Yunfei Jiang <yunjiang>
Component: RHCOSAssignee: Micah Abbott <miabbott>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Nguyen <mnguyen>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: bbreard, imcleod, jligon, nstielau, tsze, wking
Target Milestone: ---Keywords: Regression
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1877069 (view as bug list) Environment:
Last Closed: 2020-09-08 19:20:20 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:
Bug Depends On:    
Bug Blocks: 1877069, 1877070    

Description Yunfei Jiang 2020-09-08 04:10:02 UTC
Description of problem:

Scale up a cluster with RHEL 7.8, checking the cri-o version against RHCOS and RHEL:

Red Hat Enterprise Linux CoreOS 44.82.202009030930-0 (Ootpa)   4.18.0-193.14.3.el8_2.x86_64   cri-o://1.16.6-18.rhaos4.3.git538d861.el8
Red Hat Enterprise Linux Server 7.8 (Maipo)                    3.10.0-1127.19.1.el7.x86_64    cri-o://1.17.5-4.rhaos4.4.git7f0085b.el7


TASK [Get the detailed cri-o version from RHCOS worker] ************************
Monday 07 September 2020  18:41:17 +0800 (0:00:00.799)       0:00:08.459 ****** 
changed: [localhost] => {"changed": true, "cmd": "oc get node ip-10-0-56-49.us-east-2.compute.internal  --output=jsonpath='{.status.nodeInfo.containerRuntimeVersion}' | awk -F '//' '{print $2}' | awk -F '-' '{print $1}'\n", "delta": "0:00:00.213235", "end": "2020-09-07 18:41:17.873516", "rc": 0, "start": "2020-09-07 18:41:17.660281", "stderr": "", "stderr_lines": [], "stdout": "1.16.6", "stdout_lines": ["1.16.6"]}

TASK [Compare the RHEL nodes' cri-o major version is consistent with RHCOS] ****
Monday 07 September 2020  18:41:17 +0800 (0:00:00.379)       0:00:08.839 ****** 
failed: [localhost] (item=ip-10-0-51-48.us-east-2.compute.internal) => {"ansible_loop_var": "item", "changed": true, "cmd": "oc get node ip-10-0-51-48.us-east-2.compute.internal --output=jsonpath='{.status.nodeInfo.containerRuntimeVersion}'  | awk -F '//' '{print $2}' | awk -F '-' '{print $1}'\n", "delta": "0:00:00.207157", "end": "2020-09-07 18:41:18.284359", "failed_when_result": true, "item": "ip-10-0-51-48.us-east-2.compute.internal", "rc": 0, "start": "2020-09-07 18:41:18.077202", "stderr": "", "stderr_lines": [], "stdout": "
", "stdout_lines": ["1.17.5"]}


Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-09-07-061145

How reproducible:
100%

Steps to Reproduce:
1. install 4.4 cluster and scaleup with RHEL 7.8 on AWS
2.
3.

Actual results:
RHCOS nodes' cri-o version is not consistent with RHEL

Expected results:
RHCOS nodes' cri-o version is consistent with RHEL

Additional info:

Comment 1 Micah Abbott 2020-09-08 17:27:41 UTC
Between Aug 25 and Sep 2, the correct version of `cri-o` was no longer available in the RHAOS 4.4 repo.  The RHCOS build process looked for the best match for the `cri-o` package and selected the version from the RHAOS 4.3 repos.

I'll work with ART to make sure that the correct version of `cri-o` is re-included in the RHAOS 4.4 repo.

Comment 3 Micah Abbott 2020-09-08 19:19:47 UTC
Because of the BZ bot rules, please see https://bugzilla.redhat.com/show_bug.cgi?id=1877070 for tracking the fix in 4.4.z

Comment 4 Micah Abbott 2020-09-08 19:20:20 UTC
RHCOS 4.6 already had the correct version of `cri-o`