Bug 1706867

Summary:	[marketplace] Incorrectly reporting OperatorStatus degrading when restarting or upgrading marketplace operator
Product:	OpenShift Container Platform	Reporter:	Kevin Rizza <krizza>
Component:	OLM	Assignee:	Alexander Greene <agreene>
OLM sub component:	OperatorHub	QA Contact:	Fan Jia <jfan>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aravindh, eparis, wking
Version:	4.1.0
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Marketplace ClusterOperator reports degraded when restarting or upgrading marketplace operator. Consequence: The OpenShift upgrade tests are failing. Fix: Don't report degraded when the operator is stopped. Result: The OpenShift upgrade tests are passing again.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:28:30 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 Kevin Rizza 2019-05-06 12:24:54 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Kevin Rizza 2019-05-06 12:27:43 UTC

When the marketplace operator is stopped and restarted, it should not implicitly mark the ClusterOperator status as degrading.

Comment 2 Aravindh Puthiyaparambil 2019-05-06 17:49:37 UTC

https://github.com/operator-framework/operator-marketplace/pull/179/

Comment 3 Fan Jia 2019-05-08 05:41:05 UTC

test env:
cv:4.1.0-0.nightly-2019-05-08-012425
marketplace commit:aa37f1c1dafd0fd7faadd2a6b4c41f3c219be66f

test result:
remove the pod marketplace-operator-XXXX in the ns openshift-marketplace, and the status 'degraded'of clusteroperator marketplace won't become "True" during the recover of the marketplace operator.

Comment 4 errata-xmlrpc 2019-10-16 06:28:30 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