Tracker bug for bootimage bump in 4.7.z. This issue should block issues which need a bootimage bump to fix.
Moving back to ASSIGNED, as we want the BZ bot integration with the upstream repos to handle the BZ state
The RHCOS bug bot expects that bootimage bumps with open PRs will be in POST. Meanwhile, bootimage bump BZs often fail the OpenShift BZ bot's validation, and as a result it does not automatically move the BZ to POST. I've been doing that by hand.
Verified on 4.7.0-0.nightly-2021-10-04-202544. Boot image is updated
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.nightly-2021-10-04-202544 True False 6m1s Cluster version is 4.7.0-0.nightly-2021-10-04-202544
$ oc -n openshift-machine-api get machinesets
NAME DESIRED CURRENT READY AVAILABLE AGE
ci-ln-lz0gc6k-f76d1-v9ctm-worker-a 1 1 1 1 31m
ci-ln-lz0gc6k-f76d1-v9ctm-worker-b 1 1 1 1 31m
ci-ln-lz0gc6k-f76d1-v9ctm-worker-c 1 1 1 1 31m
ci-ln-lz0gc6k-f76d1-v9ctm-worker-f 0 0 31m
$ oc -n openshift-machine-api get machinesets/ci-ln-lz0gc6k-f76d1-v9ctm-worker-a -o yaml | grep image
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 (OpenShift Container Platform 4.7.33 bug fix 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.