Details
Major Description
To perform Interops on OCP4.9 (IBM power) , was trying harness scripts - https://gitlab.cee.redhat.com/codeready-workspaces/crw-osde2e/-/tree/master/scripts#run-code-ready-workspaces-test-harness-outside-of-osd and saw that images being used in tests scripts aren't supported on IBM power.
The images used in this repo -
1. "quay.io/crw/osd-e2e:nightly" - https://gitlab.cee.redhat.com/codeready-workspaces/crw-osde2e/-/blob/master/scripts/test-harness.pod.template.yml#L15
2. "quay.io/crw_pr/rsync:latest" - https://gitlab.cee.redhat.com/codeready-workspaces/crw-osde2e/-/blob/master/scripts/test-harness.pod.template.yml#L38
on IBM power , we could create these images locally using below changes.
1. For image "quay.io/crw/osd-e2e:nightly" - Changes made in Dockerfile - https://gitlab.cee.redhat.com/codeready-workspaces/crw-osde2e/-/blob/master/Dockerfile
// code placeholder
#FROM registry.ci.openshift.org/openshift/release:golang-1.15 AS builder
FROM registry.access.redhat.com/ubi8/go-toolset:1.15.14-3 as builder
USER root
After completing the setup locally on power VM - https://gitlab.cee.redhat.com/codeready-workspaces/crw-osde2e#setup
Can create image locally
// code placeholder # podman build -t quay.io/ghatwala/osd-e2e:latest . STEP 1: FROM registry.access.redhat.com/ubi8/go-toolset:1.15.14-3 AS builder STEP 2: USER root --> Using cache ef2d218993bc085f9ea10ad5564d5c45d064ed1a1c69a1106c369561dd1f600d --> ef2d218993b STEP 3: ENV PKG=/go/src/github.com/quay.io/crw-osde2e/ --> Using cache 2432487fac927c6a766291f77f1028131cd4d89b25d21ee29898ce8b79796059 --> 2432487fac9 STEP 4: WORKDIR ${PKG} --> Using cache 105a385b394ab5b7a21e9b639abb37eed9b95e6532682c6287f6d9104acb1b5f --> 105a385b394 STEP 5: COPY . . --> Using cache 3693ab75b842c68643b271b831214ce88a74b7be84b79e117b62dcefe6df5e24 --> 3693ab75b84 STEP 6: RUN make --> Using cache 0d0d2230f3fbf95525eb934f367a27876a901bd58c9b9837b0c00bd00dc05b27 --> 0d0d2230f3f STEP 7: FROM registry.access.redhat.com/ubi7/ubi-minimal:latest STEP 8: COPY --from=builder /go/src/github.com/quay.io/crw-osde2e/bin/che-operator-test-harness che-operator-test-harness --> Using cache d2364182f50d0d500ddbe64c5f6a8b2ba14fff8287c96453ada10d62da49e45c --> d2364182f50 STEP 9: COPY --from=builder /go/src/github.com/quay.io/crw-osde2e/samples samples --> Using cache 2ec3ee195f96f9f841d270d0587b98855b5e6ea50a3381bd925d7e1ed5a59a89 --> 2ec3ee195f9 STEP 10: ENTRYPOINT [ "/che-operator-test-harness" ] --> Using cache 8885051057f5fb127842b378eb27279cd2f91f7b8bee83bce3e01111f399ce11 STEP 11: COMMIT quay.io/ghatwala/osd-e2e:latest --> 8885051057f Successfully tagged quay.io/ghatwala/osd-e2e:latest 8885051057f5fb127842b378eb27279cd2f91f7b8bee83bce3e01111f399ce11
2. Second image - "quay.io/crw_pr/rsync:latest" can be created using dockerfile from here - https://github.com/eea/eea.docker.rsync/blob/master/Dockerfile , no code changes needed and just need to build this on IBM power node.
How can we handle making these images in "quay.io/crw" as multi-arch ? so that interops harness tests can be performed directly on IBM power.
