Bug 1898118

Summary: Lack of logs on some image stream tests make hard to find root cause of a problem
Product: OpenShift Container Platform Reporter: Ricardo Maraschini <rmarasch>
Component: ImageStreamsAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, jokerman, obulatov
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:33:27 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:
Attachments:
Description Flags
List of deployments during failure none

Description Ricardo Maraschini 2020-11-16 12:53:46 UTC 
Created attachment 1729751 [details]
List of deployments during failure

Description of problem:

Tests below do not log enough information to make it clear why the ephemeral image registry deployment is failing:

[sig-imageregistry][Feature:ImageStreamImport][Serial][Slow] ImageStream API TestImportRepositoryFromBlockedRegistry expand_more	5m20s
[sig-imageregistry][Feature:ImageStreamImport][Serial][Slow] ImageStream API TestImportImageFromBlockedRegistry expand_more	5m20s
[sig-imageregistry][Feature:ImageStreamImport][Serial][Slow] ImageStream API TestImportImageFromInsecureRegistry expand_more	5m20s
[sig-imageregistry][Feature:ImageStreamImport][Serial][Slow] ImageStream API TestImportRepositoryFromInsecureRegistry	5m20s

By looking at the gather-extra information I could see that the deployments did not contain anything on their statuses. By increasing the log verbosity we can at least see what was on the deployment status and how long it is taking to succeed.


How reproducible:

Not able to tell how often it does happen, but you might find useful info through https://testgrid.k8s.io/redhat-openshift-ocp-release-4.7-blocking#release-openshift-ocp-installer-e2e-aws-4.7


Expected results:

On failure we can see where exactly it failed and what was registered in the deployment statuses (conditions, available replicas, etc).


Additional info:

This might be an outcome of recent docker.io limiting. Follow attached here the list of deployments during the failure, we can see that there is no "status" on ephemeral registry deployments (we could see the deployments on gather-extra just by luck as the namespaces were already flagged to be deleted).
Comment 2 Wenjing Zheng 2020-11-25 06:33:57 UTC 
Checked several tests links and all succeeds:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/24887/pull-ci-openshift-origin-master-e2e-aws-image-registry/1330876484222455808
Comment 5 errata-xmlrpc 2021-02-24 15:33:27 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.7.0 security, bug fix, and enhancement 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-2020:5633