Closing as 4.10.67 is the last supported z stream. There will not be a 4.10.68 to push this on a boot image update unless the a customer with a support extension needs it.

It looks like https://amd64.ocp.releases.ci.openshift.org/releasestream/4-stable/release/4.10.67 has the fix, we can now do an image bump.

4.10.66 still does not have the updated ostree but the latest accepted nightly does (https://releases-rhcos-art.apps.ocp-virt.prod.psi.redhat.com/contents.html?stream=prod/streams/4.10&release=410.84.202308260035-0&arch=x86_64). Next zstream will allow us to do the image bump.

While the fixes are tagged for 4.10, this needs to be moved to MODIFIED after we have a boot image bump merged.

build has been tagged by art, waiting on a nightly with the updated ostree.

https://bugzilla.redhat.com/show_bug.cgi?id=2224109 has been verified, now waiting on: https://issues.redhat.com/browse/ART-7471 to expedite the fix into 4.10

The build we will need to tag for 4.10 is: https://bugzilla.redhat.com/show_bug.cgi?id=2224109 which still needs to be verified. Working on verification steps for RHEL 8.4...

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/