@jpoulin @chanphil.com Can you please help with verification? This should be available now in rc7: https://s390x.ocp.releases.ci.openshift.org/releasestream/4-stable-s390x/release/4.10.0-rc.7
Folks, 1. We tested with the OCP 4.10.0-rc.7 build and unfortunately we encounter the same manifest invalid issue with the disconnected install mirror registry: sha256:2a1588ed0f99e238e284d4dff10f60d180c892941c8e4d95dce4684e8452ed43 bastion:5000/ocp4/openshift4:4.10.0-rc.7-s390x-vsphere-csi-driver-operator sha256:2a1588ed0f99e238e284d4dff10f60d180c892941c8e4d95dce4684e8452ed43 bastion:5000/ocp4/openshift4:4.10.0-rc.7-s390x-vsphere-csi-driver-syncer sha256:2a1588ed0f99e238e284d4dff10f60d180c892941c8e4d95dce4684e8452ed43 bastion:5000/ocp4/openshift4:4.10.0-rc.7-s390x-vsphere-problem-detector error: unable to push manifest to bastion:5000/ocp4/openshift4:4.10.0-rc.7-s390x-machine-os-content: manifest invalid: manifest invalid info: Mirroring completed in 1m26.84s (91.55MB/s) error: one or more errors occurred while uploading images 2. FYI. The RHCOS build is the same for RC.6 and RC.7:410.84.202202251632-0 Thank you, Kyle
Moving to ASSIGNED based on comment 4. cc: @vlaad @walters
Moving to on QA awaiting validation for rc8
Thank you for the updates - We have successfully mirrored the RC.8 images for disconnected installation to our local registries. These are the images residing on the CI servers. We no longer encounter the manifest invalid error. We will continue running through our installation and upgrade tests using this build and will also verify 4.10.0-rc.8 when it becomes available on quay.io. Thank you, Phil
We have now successfully completed all our disconnected install and upgrade tests using OCP 4.10.0-rc.8 and RHCOS 410.84.202202251632-0. We used RC.8 from both CI and quay.io. This was covered on both KVM and zVM platforms. Note that the tests for the disconnected upgrade from OCP 4.9, we used OCP 4.9.22 since the latest 4.9.23 currently has the manifest invalid issue.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days