OKD OS doesn't come with MCD included, so it needs to be extracted from MCO image early in the boot. This is implemented via running `cat` command in the container to ensure that the binary is copied atomically. Since F35 bump `podman run ... --entrypoint=cat ...` no longer exists correctly, so we have to fall back to `podman run ... -v /run/bin:/host/run/bin ... --entrypoint=cp ...` to copy the binary from container. This is not an atomic operation, but at least this method is being regularly tested upstream.
This BZ was breaking only OKD nightlies aws tests. OCP is not affected by this BZ. Moved to VERIFIED.
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.10.3 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:0056