1724430 – OCP 4.2 is using CRIO 1.13.9-1.rhaos4.1.gitd70609a.el8

Bug 1724430 - OCP 4.2 is using CRIO 1.13.9-1.rhaos4.1.gitd70609a.el8

Summary: OCP 4.2 is using CRIO 1.13.9-1.rhaos4.1.gitd70609a.el8

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Containers
Sub Component:
Version:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	---
Target Release:	4.2.0
Assignee:	Lokesh Mandvekar
QA Contact:	weiwei jiang
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-06-27 05:28 UTC by Liang Xia
Modified:	2019-10-16 06:32 UTC (History)
CC List:	8 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-10-16 06:32:41 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2019:2922	0	None	None	None	2019-10-16 06:32:53 UTC

Description Liang Xia 2019-06-27 05:28:07 UTC

Description of problem:
OCP 4.2 is using CRIO 1.13.9-1.rhaos4.1.gitd70609a.el8,
but we are supposed to use 1.14.z.rhaos4.2.*


Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-06-26-211837
Client Version: version.Info{Major:"4", Minor:"2+", GitVersion:"v4.2.0", GitCommit:"250bfaa6f", GitTreeState:"clean", BuildDate:"2019-06-27T02:28:53Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.0+e965019", GitCommit:"e965019", GitTreeState:"clean", BuildDate:"2019-06-26T19:18:36Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}


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
ip-10-0-131-25.us-east-2.compute.internal    Ready    worker   176m   v1.14.0+04ae0f405   10.0.131.25    <none>        Red Hat Enterprise Linux CoreOS 420.8.20190626.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-138-32.us-east-2.compute.internal    Ready    master   3h7m   v1.14.0+04ae0f405   10.0.138.32    <none>        Red Hat Enterprise Linux CoreOS 420.8.20190626.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-154-128.us-east-2.compute.internal   Ready    worker   176m   v1.14.0+04ae0f405   10.0.154.128   <none>        Red Hat Enterprise Linux CoreOS 420.8.20190626.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-154-39.us-east-2.compute.internal    Ready    master   3h7m   v1.14.0+04ae0f405   10.0.154.39    <none>        Red Hat Enterprise Linux CoreOS 420.8.20190626.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-168-160.us-east-2.compute.internal   Ready    master   3h7m   v1.14.0+04ae0f405   10.0.168.160   <none>        Red Hat Enterprise Linux CoreOS 420.8.20190626.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8


Expected results:
Show CRIO as version 1.14-z.rhaos4.2

Additional info:

Comment 1 Lokesh Mandvekar 2019-06-28 18:04:21 UTC

dependency issues tracked at https://projects.engineering.redhat.com/browse/RCM-60926

Comment 2 Liang Xia 2019-07-15 02:36:13 UTC

Checked again on 4.2.0-0.nightly-2019-07-14-223254, we are using CRIO 1.14 now.

$ oc get nodes -o wide
NAME                                     STATUS   ROLES    AGE   VERSION             INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                                                   KERNEL-VERSION               CONTAINER-RUNTIME
qe-lxia-0714-223254-6ctbh-master-0       Ready    master   52m   v1.14.0+cb2a24bd5   10.0.0.6      <none>        Red Hat Enterprise Linux CoreOS 420.8.20190714.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.14.6-1.rhaos4.2.el8
qe-lxia-0714-223254-6ctbh-master-1       Ready    master   51m   v1.14.0+cb2a24bd5   10.0.0.4      <none>        Red Hat Enterprise Linux CoreOS 420.8.20190714.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.14.6-1.rhaos4.2.el8
qe-lxia-0714-223254-6ctbh-master-2       Ready    master   52m   v1.14.0+cb2a24bd5   10.0.0.5      <none>        Red Hat Enterprise Linux CoreOS 420.8.20190714.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.14.6-1.rhaos4.2.el8
qe-lxia-0714-223254-6ctbh-worker-5jsnp   Ready    worker   44m   v1.14.0+cb2a24bd5   10.0.32.4     <none>        Red Hat Enterprise Linux CoreOS 420.8.20190714.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.14.6-1.rhaos4.2.el8
qe-lxia-0714-223254-6ctbh-worker-wtdwj   Ready    worker   44m   v1.14.0+cb2a24bd5   10.0.32.5     <none>        Red Hat Enterprise Linux CoreOS 420.8.20190714.0 (Ootpa)   4.18.0-80.4.2.el8_0.x86_64   cri-o://1.14.6-1.rhaos4.2.el8

Comment 3 Steve Milner 2019-07-15 15:25:42 UTC

Based on the update above should this be considered verified?

Comment 4 Liang Xia 2019-07-16 01:05:10 UTC

Once the bug is ON_QA, QA can move it to verified.

Comment 5 Liang Xia 2019-07-16 03:39:31 UTC

Move to verified as the issue describe in the bug has been fixed.

Comment 6 errata-xmlrpc 2019-10-16 06:32:41 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-2019:2922

Note You need to log in before you can comment on or make changes to this bug.