Bug 1748436

Summary:	Must-gather does not collect information from the image registry
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Image Registry	Assignee:	Adam Kaplan <adam.kaplan>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Image registry's cluster-operator did not register the openshift-image-registry namespace as a related object. Consequence: In some situations, no data from the image-registry or cluster-image-registry-operator would be collected from must-gather Fix: Ensure the openshift-image-registry namespace is always included in the cluster operator's related objects Result: Basic information from the openshift-image-registry namespace (pods, deployments, services, etc.) is always collected by must-gather	Story Points:	---
Clone Of:
Clones:	1748995 (view as bug list)		Environment:
Last Closed:	2019-10-16 06:39:51 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:
Bug Depends On:
Bug Blocks:	1746155, 1748995

Description Adam Kaplan 2019-09-03 15:01:39 UTC

Description of problem: In some scenarios, the must-gather tool does not collect any information from the openshift-image-registry namespace.


Version-Release number of selected component (if applicable): 4.1.0


How reproducible: Some scenarios, such as having an improperly configured proxy.


Steps to Reproduce:
1. Install a cluster with a bad proxy configured.
2. Run the must-gather tool
3.

Actual results:

No data is collected from the openshift-image-registry namespace.


Expected results:

Data from openshift-image-registry (pod logs, secrets, ConfigMaps, etc.) are present.


Additional info: Identified in #1746155

Comment 4 errata-xmlrpc 2019-10-16 06:39:51 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, 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/RHBA-2019:2922