job: periodic-ci-openshift-ocp-installer-remote-libvirt-s390x-4.9 is failing frequently in CI, see testgrid results: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.9-informing#periodic-ci-openshift-ocp-installer-remote-libvirt-s390x-4.9 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-ocp-installer-remote-libvirt-s390x-4.9/1407399764261081088 The test case "Import the release payload "latest" from an external source" fails with the following: ``` could not run steps: step [release:latest] failed: unable to find the 'cli' image in the provided release image: the pod ci-op-5bjj6h3c/release-images-latest-cli failed after 15s (failed containers: release): ContainerFailed one or more containers exited ``` The reason seems to be that the ci-operator cannot run the extracted s390x CLI image on the build cluster which is amd64. Tracked in JIRA: https://issues.redhat.com/browse/DPTP-2265 Setting component as Multi-Arch even though the problem is likely going to be addressed in ci-tools.
Assigning this to Deep. Also setting "Blocker-" as the bug is not a blocker for 4.9. Please feel free to re-set if the bug affects other releases.
Would https://github.com/openshift/oc/pull/816 help with that?
Hi Deep - do you think this bug will be resolved before the end of the current sprint (July 3rd)? If not, can we set "reviewed-in-Sprint" flag?
We should be able to close it this sprint.
https://issues.redhat.com/browse/DPTP-2265
https://github.com/openshift/ci-tools/pull/2144
https://github.com/openshift/release/pull/20190 Last missing piece
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.9.0 bug fix and 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-2021:3759