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

Bug 1746051

Summary:	[4.2]operator-lifecycle-manager/operator-lifecycle-manager-catalog clusteroperator degraded reporting missing reason/detail information
Product:	OpenShift Container Platform	Reporter:	Evan Cordell <ecordell>
Component:	OLM	Assignee:	Jeff Peeler <jpeeler>
OLM sub component:	OLM	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	ecordell, jfan, jiazha, juzhao
Version:	4.2.0
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1741070	Environment:
Last Closed:	2019-09-04 02:09:50 UTC	Type:	---
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:	1741070

Comment 1 Jeff Peeler 2019-08-29 20:19:40 UTC

As far as I can tell, the only place that degraded true is set has a message:
https://github.com/operator-framework/operator-lifecycle-manager/blob/02c3e06da1630e53817cb5df4aaf6f270a05ba2e/pkg/lib/operatorstatus/status.go#L186

If I close this bug, than I have confirmed that to be true (both operators share this code and the package server degraded status is not monitored).

Comment 4 Jeff Peeler 2019-09-04 02:09:50 UTC

The reason this bug was marked ON_QA is because there isn't a required code change. Given that I've now tested the functionality myself, I'm just going to close this.

https://github.com/operator-framework/operator-lifecycle-manager/pull/1024#issuecomment-527708960