Bug 1843703

Summary:	FailingOperator Alert present after CSV is successfully redeployed
Product:	OpenShift Container Platform	Reporter:	Harish Govindarajulu <hgovinda>
Component:	OLM	Assignee:	Harish Govindarajulu <hgovinda>
OLM sub component:	OLM	QA Contact:	Bruno Andrade <bandrade>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	bandrade, ecordell, krizza, nhale
Version:	4.5
Target Milestone:	---
Target Release:	4.3.z
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-07-07 14:48:25 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:	1843678
Bug Blocks:

Description Harish Govindarajulu 2020-06-03 21:23:41 UTC

This bug was initially created as a copy of Bug #1819308

I am copying this bug because: 



Description of problem:
After installing an operator who's deployment failed (via a custom catalog) a FailedOperator alert was created on cluster. 

To fix the failing Operator, I uninstalled the operator, updated the catalog with new image pull specs, and reinstalled the operator. These steps led to a successful deployment of the operator.

Unfortunately, the cluster still has the FailingOperator alert after 24 hours.

Version-Release number of selected component (if applicable):
4.4.0-rc.4

How reproducible:
At least once, should be investigated as a part of this ticket.

Steps to Reproduce:
1. Create a CSV that fails to install
2. Check that the FailingOperator alert is present
3. Delete the failing CSV
4. Update the CSV so it succeeds
5. Inspect the Alerts on the cluster.

Actual results:
FailingOperator alert is present.

Expected results:
FailingOperator alert is removed.


Additional info:

Comment 7 errata-xmlrpc 2020-07-07 14:48:25 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-2020:2805