Description of problem:
For a disconnected installation, we attempt to mirror the OCP 4.9.23-s390x content, but consistently fails on image 4.9.23-s390x-machine-os-content with manifest invalid.

This is the command we issue to directly push the release images to our local registry:

1. oc adm -a ${LOCAL_SECRET_JSON} release mirror --from=quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE} --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE} --apply-release-image-signature

The majority of the images are pushed to our local registry, until the following error occurs:

...
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-kuryr-controller
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-pod
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-vsphere-csi-driver
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-vsphere-csi-driver-operator
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-vsphere-csi-driver-syncer
sha256:14e66cc7f40e3efba3fd20105ad1f40913d4fd2085ccf04e33cbfeee7127c1b5 bastion:5000/ocp4/openshift4:4.9.23-s390x-vsphere-problem-detector
error: unable to push manifest to bastion:5000/ocp4/openshift4:4.9.23-s390x-machine-os-content: manifest invalid: manifest invalid
info: Mirroring completed in 930ms (0B/s)
error: one or more errors occurred while uploading images

Version-Release number of selected component (if applicable):
OCP 4.9.23

How reproducible:
Consistently reproducible.

Steps to Reproduce:
1. Have a mirror-registry container started and running:

1. podman ps
   CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
   f875644decab docker.io/ibmcom/registry-s390x:2.6.2.5 registry serve /e... 4 hours ago Up 2 hours ago 0.0.0.0:5000->5000/tcp mirror-registry
   2. Issue the command to push content to this local registry:
2. oc adm -a ${LOCAL_SECRET_JSON} release mirror --from=quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE} --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE} --apply-release-image-signature
   3. Fails with
   error: unable to push manifest to bastion:5000/ocp4/openshift4:4.9.23-s390x-machine-os-content: manifest invalid: manifest invalid

Actual results:
A manifest invalid error occurs for image file 4.9.23-s390x-machine-os-content.

Expected results:
All 4.9.23 image files should be pushed to our local registry successfully.

Additional info: