Bug 1764411

Summary:	OCP 4.3 is using CRIO 1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8
Product:	OpenShift Container Platform	Reporter:	Liang Xia <lxia>
Component:	Containers	Assignee:	Mrunal Patel <mpatel>
Status:	CLOSED ERRATA	QA Contact:	weiwei jiang <wjiang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	aos-bugs, dwalsh, jokerman
Target Milestone:	---
Target Release:	4.3.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-01-23 11:08:59 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 Liang Xia 2019-10-23 03:32:32 UTC

Description of problem:
OCP 4.3 is using CRIO 1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8,
but we are supposed to use 1.16.z.rhaos4.3.*


Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-10-21-082726


How reproducible:
Always

Steps to Reproduce:
1. Check nodes
$ oc get nodes -o wide

Actual results:
$ oc get nodes -o wide
NAME                                             STATUS   ROLES    AGE   VERSION                    INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                                                   KERNEL-VERSION                CONTAINER-RUNTIME
qe-lxi-fzkpq-m-0.c.openshift-qe.internal         Ready    master   25h   v1.16.0-beta.2+082e1b52c   10.0.0.5                    Red Hat Enterprise Linux CoreOS 43.80.20191020.3 (Ootpa)   4.18.0-80.11.2.el8_0.x86_64   cri-o://1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8
qe-lxi-fzkpq-m-1.c.openshift-qe.internal         Ready    master   24h   v1.16.0-beta.2+082e1b52c   10.0.0.4                    Red Hat Enterprise Linux CoreOS 43.80.20191020.3 (Ootpa)   4.18.0-80.11.2.el8_0.x86_64   cri-o://1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8
qe-lxi-fzkpq-m-2.c.openshift-qe.internal         Ready    master   24h   v1.16.0-beta.2+082e1b52c   10.0.0.3                    Red Hat Enterprise Linux CoreOS 43.80.20191020.3 (Ootpa)   4.18.0-80.11.2.el8_0.x86_64   cri-o://1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8
qe-lxi-fzkpq-w-a-7z9sp.c.openshift-qe.internal   Ready    worker   24h   v1.16.0-beta.2+082e1b52c   10.0.32.2                   Red Hat Enterprise Linux CoreOS 43.80.20191020.3 (Ootpa)   4.18.0-80.11.2.el8_0.x86_64   cri-o://1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8
qe-lxi-fzkpq-w-b-c5km4.c.openshift-qe.internal   Ready    worker   24h   v1.16.0-beta.2+082e1b52c   10.0.32.3                   Red Hat Enterprise Linux CoreOS 43.80.20191020.3 (Ootpa)   4.18.0-80.11.2.el8_0.x86_64   cri-o://1.14.11-0.23.dev.rhaos4.2.gitc41de67.el8


Expected results:
Show CRIO as version 1.16-z.rhaos4.3

Additional info:

Comment 2 weiwei jiang 2019-11-11 06:35:45 UTC

Checked with 
➜  ~ oc version 
Client Version: v4.3.0
Server Version: 4.3.0-0.nightly-2019-11-10-185106
Kubernetes Version: v1.16.2

And cri-o is cri-o-1.16.0-1.rhaos4.3.el8.x86_64 now.

Comment 4 errata-xmlrpc 2020-01-23 11:08:59 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:0062