Bug 1974650 - dockerv1client fails on docker rate limits
Summary: dockerv1client fails on docker rate limits
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: Xingxing Xia
URL:
Whiteboard: EmergencyRequest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-22 08:50 UTC by Stefan Schimanski
Modified: 2021-06-22 10:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-22 10:58:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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. ***
Comment 5 Stefan Schimanski 2021-06-22 10:58:40 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.