Bug 1974651

Summary: dockerv1client tests fail due to unavailability of v1 API on registry-1.docker.io
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: openshift-apiserverAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: urgent    
Version: 4.9CC: aos-bugs, mfojtik, xxia
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: EmergencyRequest
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:35:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Schimanski 2021-06-22 08:52:02 UTC
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

Comment 1 Michal Fojtik 2021-06-22 09:20:55 UTC
** 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.

Comment 2 Stefan Schimanski 2021-06-22 10:58:37 UTC

*** This bug has been marked as a duplicate of bug 1974650 ***

Comment 3 Xingxing Xia 2021-06-23 08:48:41 UTC
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.

Comment 4 Oleg Bulatov 2021-06-23 09:11:34 UTC
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.

Comment 6 Wenjing Zheng 2021-07-08 07:17:03 UTC
Verified with the update, no TestRegistryClientDockerHubV1 now.

Comment 9 errata-xmlrpc 2021-10-18 17:35:57 UTC
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