1, Create an OCP cluster with the fixed PR via cluster-bot mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.ci.test-2022-07-14-025208-ci-ln-vjjvq4k-latest True False 4m28s Cluster version is 4.11.0-0.ci.test-2022-07-14-025208-ci-ln-vjjvq4k-latest 2, Do a regression test. mac:~ jianzhang$ oc get pods -n openshift-marketplace NAME READY STATUS RESTARTS AGE 6518c26c328d59c33d7d6f89fe65ea07b7a25557afff7e96715335bed7s8pgd 0/1 Completed 0 7m12s 96696e0506a4eba64778179a5ae569ea7b881e9f37a48113754cba904dtbdhq 0/1 Completed 0 5m17s certified-operators-x4d88 1/1 Running 0 37m community-operators-g859j 1/1 Running 0 37m e8c9651078ae45ddb2807e3a07727d459b82d7def5572a7b7ccaae332bmgzt8 0/1 Completed 0 9m51s marketplace-operator-54855dcbcd-5rvpk 1/1 Running 1 (25m ago) 44m redhat-marketplace-xnpv6 1/1 Running 0 37m redhat-operators-9rc2p 1/1 Running 0 37m No issue found for the containerd version updated, verify it.
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.11.1 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-2022:6103