Bug 1908919

Summary:	[sig-imageregistry][Feature:ImageInfo] Image info should display information about images failing frequently
Product:	OpenShift Container Platform	Reporter:	jamo luhrsen <jluhrsen>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED DUPLICATE	QA Contact:	Wenjing Zheng <wzheng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.7	CC:	aos-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-17 22:41:33 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 jamo luhrsen 2020-12-17 22:37:10 UTC

This test is failing frequently in CI. for 4.7, it looks like it's see in ~15% of failing jobs:

https://search.ci.openshift.org/?search=Image+info+should+display+information+about+images&maxAge=48h&context=1&type=build-log&name=4.7&maxMatches=5&maxBytes=20971520&groupBy=job

Here's a job where it's happening very frequently 2/3rds of the failed jobs have it:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.7-informing#periodic-ci-openshift-release-master-ocp-4.7-e2e-vsphere&sort-by-flakiness=he

in this job that has the failure:
https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-vsphere/1339617845297811456

I do see that it was affected by docker rate limiting. Maybe that's related?
+ oc image info docker.io/library/mysql:latest
error: unable to read image docker.io/library/mysql: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

Comment 1 jamo luhrsen 2020-12-17 22:41:33 UTC

I found the bug already tracking this: https://bugzilla.redhat.com/show_bug.cgi?id=1904679

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