Bug 1888383 - Don't use OperatorExited in cluster operator status
Summary: Don't use OperatorExited in cluster operator status
Keywords:
Status: CLOSED DUPLICATE of bug 1838352
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-14 18:00 UTC by Kevin Rizza
Modified: 2020-10-26 13:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-26 13:49:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.