This constantly fails in unit tests: === RUN TestRegistryClientDockerHubV1 dockerregistryclient_test.go:169: error retrieving tag: server returned 503 --- FAIL: TestRegistryClientDockerHubV1 (0.72s) Compare https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_openshift-apiserver/221/pull-ci-openshift-openshift-apiserver-master-unit/1407244579077361664
** WARNING ** This BZ claims that this bug is of urgent severity and priority. Note that urgent priority means that you just declared emergency within engineering. Engineers are asked to stop whatever they are doing, including putting important release work on hold, potentially risking the release of OCP while working on this case. Be prepared to have a good justification ready and your own and engineering management are aware and has approved this. Urgent bugs are very expensive and have maximal management visibility. NOTE: This bug was assigned to engineering manager with severity reset to *unspecified* until the emergency is vetted and confirmed. Please do not manually override the severity.
*** This bug has been marked as a duplicate of bug 1974650 ***
QE CI also saw docker rate limit months ago and had fixed QE CI cases. Per this, it is more about test-only issue, not product issue, so reducing severity. And it is more about image import testing, so changing QE Contact to IR colleague.
Pushes to Docker Hub via the registry v1 API have been disallowed since November 2015, and importing via v1 API has also been deprecated in OpenShift, so we can remove this feature.
Verified with the update, no TestRegistryClientDockerHubV1 now.
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.9.0 bug fix and 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-2021:3759