-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.17.0
-
None
Description of problem:
The following sig-cli OCP Conformance test fails in OpenShift v4.17 clusters because the `ruby:3.1-ubi8` imagestreamtag cannot be found.
[sig-cli] oc set image can set images for pods and deployments [apigroup:image.openshift.io][apigroup:apps.openshift.io][Skipped:Disconnected] [Suite:openshift/conformance/parallel]
We believe https://github.com/openshift/origin/pull/29162/files#diff-7bfeda4ac78d4fa4e863e9d2f964d0e2983130b8e55c4cbe13c7a1ee832541c6R859 is what broke this previously functional test. Changing
"name": "registry.access.redhat.com/ubi8/ruby-30:latest" to "name": "registry.redhat.io/ubi8/ruby-31:latest" now requires auth.
The other ruby images streams in the test data use registry.access.redhat.com.
As a result, we are unable to pull it.
- conditions: - generation: 2 lastTransitionTime: "2024-10-30T22:01:41Z" message: 'Internal error occurred: registry.redhat.io/ubi8/ruby-31:latest: Get "https://registry.redhat.io/v2/ubi8/ruby-31/manifests/latest": unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication' reason: InternalError status: "False" type: ImportSuccess items: null tag: 3.1-ubi8
We believe this is a test case bug and that the `registry.redhat.io/ubi8/ruby-31:latest` reference above should go back to using the `registry.access.redhat.com`-based endpoint which doesn't require auth.
Version-Release number of selected component (if applicable):
4.17.0
How reproducible:
Running the `[sig-cli] oc set image can set images for pods and deployments [apigroup:image.openshift.io][apigroup:apps.openshift.io][Skipped:Disconnected] [Suite:openshift/conformance/parallel]` OCP conformance test against an OpenShift 4.17 cluster that doesn't have a global pull secret configured for new namespaces.
Steps to Reproduce:
1. Create an OpenShift v4.17 cluster.
2. Ensure newly created namespaces (i.e. `e2e-test-oc-set-image-xxxxx`) don't use the global pull secret.
2. Run the `[sig-cli] oc set image can set images for pods and deployments [apigroup:image.openshift.io][apigroup:apps.openshift.io][Skipped:Disconnected] [Suite:openshift/conformance/parallel]` OCP conformance test.
Actual results:
...
Error from server (NotFound): imagestreamtags.image.openshift.io "ruby:3.1-ubi8" not found [FAILED] in [It] - github.com/openshift/origin/test/extended/cli/setimage.go:45 @ 10/28/24 18:59:40.69
...
------------------------------
Summarizing 1 Failure:
[FAIL] [sig-cli] oc set image [It] can set images for pods and deployments [apigroup:image.openshift.io][apigroup:apps.openshift.io][Skipped:Disconnected] [Suite:openshift/conformance/parallel] github.com/openshift/origin/test/extended/cli/setimage.go:45
Ran 1 of 1 Specs in 123.203 seconds FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped fail [github.com/openshift/origin/test/extended/cli/setimage.go:45]: Unexpected error:
<wait.errInterrupted>:
timed out waiting for the condition
{
cause: <*errors.errorString | 0xc0003cb470>
{
s: "timed out waiting for the condition",
},
}
occurred
Ginkgo exit error 1: exit with code 1
Expected results:
The "ruby:3.1-ubi8" imagestreamtag should be found.
Additional info:
