Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Moderate: OpenShift Container Platform 4.11.30 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-2023:1030

Verified with 4.11.0-0.nightly-2023-02-22-220245

aaradhak@fedora ~ $ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2023-02-22-220245   True        False         49m     Cluster version is 4.11.0-0.nightly-2023-02-22-220245
aaradhak@fedora ~ $ oc -n openshift-machine-api get machinesets
NAME                                          DESIRED   CURRENT   READY   AVAILABLE   AGE
ci-ln-bbmjz2b-76ef8-tqgdd-worker-us-east-2a   1         1                             75m
ci-ln-bbmjz2b-76ef8-tqgdd-worker-us-east-2c   2         2         2       2           75m
aaradhak@fedora ~ $ 
aaradhak@fedora ~ $ oc -n openshift-machine-api get machineset ci-ln-bbmjz2b-76ef8-tqgdd-worker-us-east-2a -o yaml | grep ami
          ami:
            id: ami-0f2483edc1ec85f51

Thanks for reporting your issue!

In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible.

Be ready for follow-up questions and please respond in a timely manner.

If we can't reproduce a bug, we might close your issue.

OCP Version at Install Time:
RHCOS Version at Install Time:
OCP Version after Upgrade (if applicable):
RHCOS Version after Upgrade (if applicable):
Platform (AWS, Azure, bare metal, GCP, vSphere, etc.):
Architecture (x86_64, ppc64le, s390x, etc.):

If you're having problems booting/installing RHCOS, please provide:

• Reproduction steps that work with a single RHCOS node
• The full contents of the serial console showing disk initialization, network configuration, and Ignition stages. See this article for information about configuring your serial console. Screenshots or a video recording of the console is usually not sufficient.
• Ignition JSON
• Output of journalctl -b

If you're having problems post-upgrade, please provide:

• A complete must-gather (oc adm must-gather)

If you're having SELinux related issues, please provide:

• The full /var/log/audit/audit.log file
• Were any SELinux modules or booleans changed from the default configuration?
• The output of ostree admin config-diff | grep selinux/targeted on impacted nodes

Please add anything else that might be useful, for example:

• Kernel command line (cat /proc/cmdline)
• Contents of /etc/NetworkManager/system-connections/
• Contents of /etc/sysconfig/network-scripts/