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):
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.
FailingOperator alert is present.
FailingOperator alert is removed.
Alerts were removed after the Operator issue was fixed. Marking as VERIFIED.
OCP Version: 4.5.0-0.nightly-2020-06-20-194346
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.