Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1974650

Summary: dockerv1client fails on docker rate limits
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: openshift-apiserverAssignee: Oleg Bulatov <obulatov>
Status: CLOSED NOTABUG QA Contact: Xingxing Xia <xxia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.9CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: ---   
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-06-22 10:58:19 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:50:50 UTC
This seems to constantly fail:

=== RUN   TestRegistryClientDockerHubV1
    dockerregistryclient_test.go:169: error retrieving tag: server returned 503
--- FAIL: TestRegistryClientDockerHubV1 (0.72s)

Comment 1 Michal Fojtik 2021-06-22 08:50:54 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 Michal Fojtik 2021-06-22 09:50:54 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 4 Stefan Schimanski 2021-06-22 10:58:36 UTC
*** Bug 1974651 has been marked as a duplicate of this bug. ***