There are a number of issues with the test named in $SUBJECT: * it copies the oc binary from the machine running the test into a container pulled by the cluster, meaning that (depending on the system on which oc and openshift-tests are built and run) the oc binary might not be binary compatible, or even architecture compatible, with the container; * the container used is upstream origin-control-plane:3.11, which seems unusual for testing a 4.y cluster given no such container exists in 4.y; * origin containers are not available for other architectures besides x86_64, so the test cannot pass on other cluster architectures; * even if you substitute the OCP ose-control-plane:3.11, only Power was added to 3.y, so still no help for Z (or potentially ARM in the future). Can this test be overhauled to work on all architectures, and regardless of potential differences between client and cluster architectures?
Does it cause some problems today that need to be immediately fixed?
The test fails on all !x86 architectures and therefore interferes with multi-arch enablement of the serial testsuite.
Passed in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26459/pull-ci-openshift-origin-master-e2e-aws-serial/1437469582817234944 and https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26459/pull-ci-openshift-origin-master-e2e-aws-image-registry/1437469582766903296
Unfortunately this caused failures in the serial testsuite when run on a FIPS cluster, and was reverted.
Scenario: Image signature workflow can push a signed image to openshift registry and verify it Passed in: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26515/pull-ci-openshift-origin-master-e2e-aws-serial/1447922547432624128 and: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26510/pull-ci-openshift-origin-master-e2e-aws-image-registry/1445929851142803456 especially fips cluster: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26510/pull-ci-openshift-origin-master-e2e-gcp-fips-serial/1445934123582492672
*** Bug 2007850 has been marked as a duplicate of this bug. ***
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