Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-1360

ci-operator cannot import an s390x or a non-amd64 OCP release image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 4.9.0
    • 4.9
    • Multi-Arch
    • None
    • Quality / Stability / Reliability
    • False
    • None
    • None
    • None
    • None
    • None
    • Sprint 16: 07/26 - 08/14
    • None
    • None
    • Undefined

      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.

              rh-ee-dmistry Deep Mistry
              rhn-coreos-htariq Haseeb Tariq
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: