Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1974973

Summary: ci-operator cannot import an s390x or a non-amd64 OCP release image
Product: OpenShift Container Platform Reporter: Haseeb Tariq <htariq>
Component: Multi-ArchAssignee: Deep Mistry <dmistry>
Status: CLOSED ERRATA QA Contact: Barry Donahue <bdonahue>
Severity: high Docs Contact:
Priority: medium    
Version: 4.9CC: danili, dmistry, yselkowi
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
job=periodic-ci-openshift-ocp-installer-remote-libvirt-s390x-4.9=all failed: unable to find the 'cli' image in the provided release image
Last Closed: 2021-10-18 17:36:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Haseeb Tariq 2021-06-22 21:13:02 UTC 
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.
Comment 1 Dan Li 2021-06-23 13:55:00 UTC 
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.
Comment 2 Yaakov Selkowitz 2021-06-24 17:43:54 UTC 
Would https://github.com/openshift/oc/pull/816 help with that?
Comment 3 Dan Li 2021-06-28 18:26:02 UTC 
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?
Comment 4 Deep Mistry 2021-06-28 20:31:00 UTC 
We should be able to close it this sprint.
Comment 5 Deep Mistry 2021-07-09 14:15:49 UTC 
https://issues.redhat.com/browse/DPTP-2265
Comment 6 Deep Mistry 2021-07-09 14:38:20 UTC 
https://github.com/openshift/ci-tools/pull/2144
Comment 7 Deep Mistry 2021-07-21 14:21:15 UTC 
https://github.com/openshift/release/pull/20190 Last missing piece
Comment 11 errata-xmlrpc 2021-10-18 17:36:21 UTC 
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