Description of problem: cri-o version in RHCOS is older than that in RHEL Version-Release number of selected component (if applicable): # oc version Client Version: 4.5.0-0.nightly-2020-04-07-093009 Server Version: 4.5.0-0.nightly-2020-04-07-093009 Kubernetes Version: v1.18.0-rc.1 How reproducible: Always Steps to Reproduce: 1. Set up a cluster 2. Check cri-o version via `oc get node -o wide` command, it is `v1.17.1` # oc get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME yy3878-xhgz5-m-0.c.openshift-qe.internal Ready master 93m v1.17.1 10.0.0.3 Red Hat Enterprise Linux CoreOS 45.81.202004070601-0 (Ootpa) 4.18.0-147.5.1.el8_1.x86_64 cri-o://1.17.0-9.dev.rhaos4.4.gitdfc8414.el8 3. Scale up some rhel worker, the scaled rhel worker is using ` v1.18.0-rc.1` cri-o Actual results: The cri-o version is out-of-date, even older than the one in rhel worker. Expected results: cri-o keep up-to-date, keep consistent with rhel worker. Additional info:
In mix rhcos and rhel worker cluster testing, keep consistent cri-o verison is an important test point in QE's testing, this is blocking QE's testing. I am not sure we should use lower version of cri-o in RHEL worker, or bump up version of cri-o in rhcos? Adding "testblocker" keyword.
I'm not sure how RHEL worker nodes are getting `cri-o` 1.18...there is no 1.18 build available in Brew yet. That version string being reported looks like the version of kubernetes. Please check the output of `rpm -q cri-o` on the RHEL worker nodes to confirm the version of the `cri-o` package. The current expectation is that RHCOS and RHEL are using the same 1.17 version of `cri-o`. Closing as NOTABBUG; please re-open if you can confirm the RHEL nodes have a different `cri-o` RPM installed.
The RHEL actually requires cri-o 1.18 but the 1.18 build is not available yet. We have a bz against release, please check out Bug 1821567 - cri-o-1.18 required by AOS4.5 RHEL scaleup is not found. Re-opening it. We can close it if RHEL reverts to 1.17.
Changing this to low pri/sev because it should be pretty obvious when the 1.18 builds are available and RHCOS should pick them up automagically.
Install a cluster with 4.5.0-0.nightly-2020-04-21-040933. # oc get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME yanyan-n4b5h-m-0.c.openshift-qe.internal Ready master 24h v1.18.0-rc.1 10.0.0.5 Red Hat Enterprise Linux CoreOS 45.81.202004210032-0 (Ootpa) 4.18.0-147.8.1.el8_1.x86_64 cri-o://1.18.0-3.dev.rhaos4.5.git2cef6c3.el8-rc2 RHCOS installs 1.18 build hence move it to verified state.
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