Image manifest error when mirroring images for a disconnected installation

Solution In Progress - Updated -

Issue

  • The error happens when the following command (or similar) is executed:
# 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
  • Many images are usually pushed without any problem, but the process becomes interrupted at some point. Example of errors returned:
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

Environment

  • Red Hat OpenShift Container Platform 4.10 or earlier.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content