This is a clone of issue OCPBUGS-73848. The following is the description of the original issue:
—
The oauth-proxy e2e-component tests fail on OCP 4.22 because RHEL 9 enforces fully qualified container image names ("short name mode").

The backend test image nginxdemos/nginx-hello:plain-text is rejected by Podman since it cannot determine which registry to pull from.

Version-Release number

4.22

How reproducible

Always

Steps to Reproduce

Run the oauth-proxy e2e-component tests on OCP 4.22

The test creates a pod with a backend container using image nginxdemos/nginx-hello:plain-text

Observe the pod fails to start.

Actual results

The backend container fails with:

ImageInspectError: short name mode is enforcing, but image name 
nginxdemos/nginx-hello:plain-text returns ambiguous list

The pod never reaches Running state, and all e2e tests fail.

Expected results

The e2e tests should pass. The backend container should start successfully using a fully qualified image reference.

Additional info

Root cause: RHEL 9 enforces "short name mode" for container images, requiring fully qualified registry paths.

Fix: Replace nginxdemos/nginx-hello:plain-text with registry.k8s.io/e2e-test-images/agnhost:2.53, which is:

• Fully qualified (satisfies RHEL 9 short name policy)
• Multi-arch (supports ARM64)
• The standard test image adopted across OpenShift repositories (openshift/origin PR #29672)
• Mirrored in OpenShift CI infrastructure

PR: https://github.com/openshift/oauth-proxy/pull/343