Setting this as blocker+, this is the bug to be used to revert the MAO change that broke upgrades in 4.11.

Verified

upgrade the cluster 4.3.18->4.4.33->4.5.41->4.6.60->4.7.55->4.8.46->4.9.43->4.10.24->4.11.0-0.nightly-2022-07-26-154822->4.12.0-0.nightly-2022-07-27-133042, upgrade is successful. Cluster https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/124511/artifact/workdir/install-dir/auth/kubeconfig/*view*/

$ oc get clusterversion                                                               [22:44:31]
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-2022-07-27-133042   True        False         166m    Cluster version is 4.12.0-0.nightly-2022-07-27-133042

in 4.11.0-0.nightly-2022-07-26-154822
$ oc edit deploy machine-api-operator
      securityContext:
        runAsNonRoot: true
        runAsUser: 65534

in 4.12.0-0.nightly-2022-07-27-133042
$ oc edit deploy machine-api-operator
      securityContext: {}

$ oc get pods -A | grep CreateContainerConfigError 
$

Removing UpgradeBlocker since no request to block edges has been forthcoming and no obvious signs of a significant % of the fleet being impacted. This is based upon impact statement https://bugzilla.redhat.com/show_bug.cgi?id=2108858#c8.

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 (Important: OpenShift Container Platform 4.11.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-2022:5069