Before reporting an issue
Area
testsuite
Describe the bug
Inside the testsuite's K8sUtils.java, the createCurlContainer method creates a new pod, referencing a particular image coordinate (curlimages/curl:8.1.2) that does not specify an image registry. This, by deprecated convention, implicitly means to use DockerHub as the registry for the image. There are two problems with this:
- Kubernetes systems that have fully deprecated the old convention (such as OpenShift Container Platform 4.21) now refuse to accept image coordinates that do not specify a registry.
- DockerHub frequently applies rate limiting that can cause test failures for no reason.
Replacing this image coordinate with quay.io/curl/curl:8.1.2 would resolve these problems, while providing the same image that the tests depend on.
Version
main
Regression
Expected behavior
Test cases relying on the createCurlContainer method should work on OCP 4.21
Actual behavior
Test cases relying on the createCurlContainer method fail to start due to OCP refusing to accept an unqualified image coordinate.
How to Reproduce?
Run the testsuite with OCP 4.21
Anything else?
No response
Before reporting an issue
Area
testsuite
Describe the bug
Inside the testsuite's K8sUtils.java, the createCurlContainer method creates a new pod, referencing a particular image coordinate (
curlimages/curl:8.1.2) that does not specify an image registry. This, by deprecated convention, implicitly means to use DockerHub as the registry for the image. There are two problems with this:Replacing this image coordinate with
quay.io/curl/curl:8.1.2would resolve these problems, while providing the same image that the tests depend on.Version
main
Regression
Expected behavior
Test cases relying on the createCurlContainer method should work on OCP 4.21
Actual behavior
Test cases relying on the createCurlContainer method fail to start due to OCP refusing to accept an unqualified image coordinate.
How to Reproduce?
Run the testsuite with OCP 4.21
Anything else?
No response