Bug 1888383

Summary:	Don't use OperatorExited in cluster operator status
Product:	OpenShift Container Platform	Reporter:	Kevin Rizza <krizza>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OperatorHub	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	nhale, wking
Version:	4.6	Keywords:	UpcomingSprint
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-26 13:49:12 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 2020-10-14 18:00:06 UTC

Description of problem:

When the marketplace operator exits, it sets the cluster operator status as "OperatorExited". That status is not valuable as it just creates extra noise when pods are potentially rescheduled, and an alert is fired if the deployment is truly unhealthy anyway.

How reproducible:
Always

Steps to Reproduce:
1. Restart marketplace pod
2. Watch the operator status be set to OperatorExited once the operator shuts down gracefully

Actual results:
OperatorExited status is set

Expected results:
OperatorExited status shouldn't be set or used

Comment 2 Evan Cordell 2020-10-26 13:49:12 UTC


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