Description of problem: Tests `[sig-builds][Feature:Builds] s2i build with a root user image .*` use the image docker.io/openshift/test-build-roots2i. As docker.io has rate limits, we should avoid using it. Actual results: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/368/pull-ci-openshift-ovn-kubernetes-master-e2e-vsphere-ovn/1335204821283639296 [sig-builds][Feature:Builds] s2i build with a root user image should create a root build and pass with a privileged SCC W1205 13:40:01.764563 14771 dockerimagelookup.go:237] container image registry lookup failed: docker.io/openshift/test-build-roots2i:latest: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit error: unable to locate any images in image streams, local docker images with name "docker.io/openshift/test-build-roots2i" Additional info: https://search.ci.openshift.org/?search=failed%3A.*s2i+build+with+a+root+user+image&maxAge=48h&context=1&type=build-log&name=master-e2e&maxMatches=5&maxBytes=20971520&groupBy=job
Had not caught that one Oleg - thanks I'll add an update to this to https://github.com/openshift/origin/pull/25740 Once that is done I'll close this as a dup to the bug associated with that PR.
well actually we may have to create a new image on quay.io for this one ... if that takes too long I'll sort this one out separately
PR CI sufficient verification
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.7.0 security, bug fix, and enhancement 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-2020:5633