Bug 1793953
| Summary: | cri-o version get out-of-date in 44.81.202001212027.0 rhcos | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Node | Assignee: | Urvashi Mohnani <umohnani> |
| Status: | CLOSED ERRATA | QA Contact: | Sunil Choudhary <schoudha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4 | CC: | amurdaca, aos-bugs, bbreard, dustymabe, imcleod, jligon, jokerman, nstielau, rphillips, schoudha, weinliu |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-04 11:25:48 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: | |||
RHCOS was asked to revert to `cri-o` 1.16 due to https://bugzilla.redhat.com/show_bug.cgi?id=1792749 It appears the breakage described in that BZ happened around the same time the bump to `cri-o` 1.17 occurred. The breakage was preventing any merges from happening, so this temporary rollback to 1.16 was introduced. @runcom do we have more confidence that the `cri-o` bump was the root cause of BZ#1792749 ? I'm moving this to Node team as we had to rollback CRI-O in CI to 1.16 because CRI-O 1.17 has a bug that breaks the MCO CI (In reply to Micah Abbott from comment #1) > RHCOS was asked to revert to `cri-o` 1.16 due to > https://bugzilla.redhat.com/show_bug.cgi?id=1792749 > > It appears the breakage described in that BZ happened around the same time > the bump to `cri-o` 1.17 occurred. > > The breakage was preventing any merges from happening, so this temporary > rollback to 1.16 was introduced. > > @runcom do we have more confidence that the `cri-o` bump was the root cause > of BZ#1792749 > ? the revert has fixed the MCO CI so yeah that has been the root cause of that other BZ *** Bug 1800509 has been marked as a duplicate of this bug. *** OCP 4.4 now has the most recent version of cri-o - 1.17. 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:0581 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: Version-Release number of the following components: registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-01-21-233101 How reproducible: Always Steps to Reproduce: 1. Using the payload to set up a cluster 2. Check cri-o version via `oc get node -o wide` command, it is `1.16.2` 3. Scale up some rhel worker, the scaled rhel working is using `1.17.0` 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 4.4.0-0.nightly-2020-01-21-233101, its machine-os-content is: # oc adm release info "${QE_OPENSHIFT_INSTALL_RELEASE_IMAGE}" --image-for machine-os-content | xargs oc image info Name: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:250355e0f0fa0bc38602133b80c0726e285efd07623b12668dfc774deb85a73d Media Type: application/vnd.docker.distribution.manifest.v2+json Created: 13h ago Image Size: 815.7MB in 1 layers Layers: 815.7MB sha256:0cc2c83b4a102e00a46642451358ef6d5a77fa248a20f7b6dbe984ebf3e7a2f5 OS: linux Arch: amd64 Entrypoint: /noentry Labels: com.coreos.ostree-commit=3a3a44042cd54280adc82c6f09d2c15d1695ffbcba85b8dca0c066e7ebb5443e io.buildah.version=1.12.0 version=44.81.202001212027.0 Check https://releases-rhcos-art.cloud.privileged.psi.redhat.com/contents.html?stream=releases%2Frhcos-4.4&release=44.81.202001212027.0, it indeed is built with cri-o 1.16.2. Compare with an older payload - 4.4.0-0.nightly-2020-01-21-202840, it is using https://releases-rhcos-art.cloud.privileged.psi.redhat.com/contents.html?stream=releases%2Frhcos-4.4&release=44.81.202001202331.0 as machine-os-content, no such issue. So this seem like a regression issue.