This bug is tracking the long-term fix, but rc.8 is fine:
$ for ARCH in aarch64 ppc64le s390x x86_64; do oc adm release info --pullspecs "quay.io/openshift-release-dev/ocp-release:4.10.0-rc.8-${ARCH}" | sed -n 's|.*\(quay.io/\)|\1|p'; done | sort | uniq | while read IMAGE; do oc image info "${IMAGE}" | grep 'Media Type'; done | sort | uniq -c
44 Media Type: application/vnd.docker.distribution.manifest.v2+json
496 Media Type: application/vnd.docker.distribution.manifest.v2+json
So this doesn't block 4.10.0. If folks feel like it should block 4.10.1, they can add blocker+ back once 4.10 is out.
The fix to `coreos-assembler:rhcos-4.10` landed in https://github.com/coreos/coreos-assembler/pull/2727
I've confirmed that the latest machine-os-content images pushed to Quay for all arches are in v2s2 format
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.10.4 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.
https://access.redhat.com/errata/RHBA-2022:0811
This bug is tracking the long-term fix, but rc.8 is fine: $ for ARCH in aarch64 ppc64le s390x x86_64; do oc adm release info --pullspecs "quay.io/openshift-release-dev/ocp-release:4.10.0-rc.8-${ARCH}" | sed -n 's|.*\(quay.io/\)|\1|p'; done | sort | uniq | while read IMAGE; do oc image info "${IMAGE}" | grep 'Media Type'; done | sort | uniq -c 44 Media Type: application/vnd.docker.distribution.manifest.v2+json 496 Media Type: application/vnd.docker.distribution.manifest.v2+json So this doesn't block 4.10.0. If folks feel like it should block 4.10.1, they can add blocker+ back once 4.10 is out.