Tracker bug for bootimage bump in 4.9. This issue should block issues which need a bootimage bump to fix. The previous bump was bug 1970179.
$ oc get clusterversion oNAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-08-30-070917 True False 32m Cluster version is 4.9.0-0.nightly-2021-08-30-070917 $ oc -n openshift-machine-api get machinesets NAME DESIRED CURRENT READY AVAILABLE AGE mnguyen49bib-5ftr7-worker-us-west-2a 1 1 1 1 56m mnguyen49bib-5ftr7-worker-us-west-2b 1 1 1 1 56m mnguyen49bib-5ftr7-worker-us-west-2c 1 1 1 1 56m mnguyen49bib-5ftr7-worker-us-west-2d 0 0 56m $ oc -n openshift-machine-api get machinesets/mnguyen49bib-5ftr7-worker-us-west-2a -o yaml | grep ami f:ami: {} ami: id: ami-0228531eacc8ad7e9
This bump is being reverted in https://github.com/openshift/installer/pull/5180. Moving back to ASSIGNED.
Since the original PR was reverted in https://github.com/openshift/installer/pull/5180 because of problems that the use of `cri-o` 1.22 introduced on the bootstrap node, we are unable to proceed with another boot image bump for 4.9 until the underlying issue is resolved. The current belief is that https://bugzilla.redhat.com/show_bug.cgi?id=1999133 is the root cause and once that is resolved, we can proceed with the boot image bump.
Marking this as a late blocker because of the following reasons: - current boot image being used in OCP 4.9 includes cri-o 1.21 and we want to start from 1.22 - can't use 1.22 until 1999133 is fixed - the boot image is also required for proper delivery of the other RHCOS blocker+ https://bugzilla.redhat.com/show_bug.cgi?id=1999577 - the current PR to `openshift/installer` is using a much older version of RHCOS on the s390x platform and is out of sync with the other arches We probably should have set this flag earlier when we understood the situation with the kubelet in 1999133 or when we identified the other RHCOS blocker in 1999577 This is more explicit about the need for this boot image bump for delivering fixes. As there is already a PR for the boot image bump to `openshift/installer`, it will be updated with newer versions of RHCOS once the kubelet BZ is fixed.
*** Bug 2004599 has been marked as a duplicate of this bug. ***
For clarity, the late addition of bug 2006962 is correct; that bug was fixed by code already in the bootimage bump.
Verified on 4.9.0-0.nightly-2021-09-23-142241 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-09-23-142241 True False 7m35s Cluster version is 4.9.0-0.nightly-2021-09-23-142241 $ oc -n openshift-machine-api get machinesets NAME DESIRED CURRENT READY AVAILABLE AGE ci-ln-n3bifxb-f76d1-7hgb7-worker-a 1 1 1 1 35m ci-ln-n3bifxb-f76d1-7hgb7-worker-b 1 1 1 1 35m ci-ln-n3bifxb-f76d1-7hgb7-worker-c 1 1 1 1 35m ci-ln-n3bifxb-f76d1-7hgb7-worker-f 0 0 35m $ oc -n openshift-machine-api get machinesets/ci-ln-n3bifxb-f76d1-7hgb7-worker-a -o yaml | grep image image: projects/rhcos-cloud/global/images/rhcos-49-84-202109172039-0-gcp-x86-64 matches boot image PR: "gcp": { "image": "rhcos-49-84-202109172039-0-gcp-x86-64", "project": "rhcos-cloud", "url": "https://storage.googleapis.com/rhcos/rhcos/rhcos-49-84-202109172039-0-gcp-x86-64.tar.gz" },
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759