Cause: When updating a Catalog Source a Get call is immediately followed by a Delete call on a number of resources related to the Catalog Source.
Consequence: In some instances, the resource has already been deleted but the resource still exists in the cache. This allows the Get call to succeed but the following delete call fails as the resource does not exist on cluster.
Fix: Updated OLM to ignore the error returned by the Delete call if the resource is not found.
Result: OLM no longer reports an error when updating a catalog due to a caching issue that results in a "Resource Not Found" error from the delete call.
DescriptionAlfredo Pizarro
2021-06-03 13:32:49 UTC
Description of problem:
There is an active OCS operator install that is stuck trying to install and OLM is complaining when it tries to delete catalog pods under openshift-marketplace:
ocs install status:
lastTransitionTime: "2021-05-26T21:42:51Z"
lastUpdateTime: "2021-05-26T21:42:51Z"
message: install timeout
phase: Failed
reason: InstallCheckFailed
Catalog source logs:
2021-05-27T17:04:57.517829141Z E0527 17:04:57.517756 1 queueinformer_operator.go:290] sync {"update" "openshift-marketplace/redhat-marketplace"} failed: couldn't ensure registry server - error ensuring updated catalog source pod: : error deleting duplicate catalog polling pod: redhat-marketplace-t9mzw: error deleting pod: redhat-marketplace-t9mzw: pods "redhat-marketplace-t9mzw" not found
But, there is no pod with that name:
$ omg get pods
NAME READY STATUS RESTARTS AGE
5bae77dfc8df1dc4e8403e4e24d9e6ee44122c82b9795de0312812d818tfxj6 0/1 Succeeded 0 6d
64df73cd6ca959f7f62e31221ffc25dfafbaf2627dded53543399c431c86qqd 0/1 Succeeded 0 15d
965304d2cdcc277b3c03a16e3490f65f85ba839251fb7ed304cd6a1ac1685ml 0/1 Succeeded 0 15d
certified-operators-5fhz4 1/1 Running 0 7h30m
community-operators-kftpt 1/1 Running 0 1h8m
marketplace-operator-6cc74874c7-kz89g 1/1 Running 0 141d
redhat-marketplace-72k4h 1/1 Running 0 5d
redhat-operators-d7frj 1/1 Running 0 16h
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759
Description of problem: There is an active OCS operator install that is stuck trying to install and OLM is complaining when it tries to delete catalog pods under openshift-marketplace: ocs install status: lastTransitionTime: "2021-05-26T21:42:51Z" lastUpdateTime: "2021-05-26T21:42:51Z" message: install timeout phase: Failed reason: InstallCheckFailed Catalog source logs: 2021-05-27T17:04:57.517829141Z E0527 17:04:57.517756 1 queueinformer_operator.go:290] sync {"update" "openshift-marketplace/redhat-marketplace"} failed: couldn't ensure registry server - error ensuring updated catalog source pod: : error deleting duplicate catalog polling pod: redhat-marketplace-t9mzw: error deleting pod: redhat-marketplace-t9mzw: pods "redhat-marketplace-t9mzw" not found But, there is no pod with that name: $ omg get pods NAME READY STATUS RESTARTS AGE 5bae77dfc8df1dc4e8403e4e24d9e6ee44122c82b9795de0312812d818tfxj6 0/1 Succeeded 0 6d 64df73cd6ca959f7f62e31221ffc25dfafbaf2627dded53543399c431c86qqd 0/1 Succeeded 0 15d 965304d2cdcc277b3c03a16e3490f65f85ba839251fb7ed304cd6a1ac1685ml 0/1 Succeeded 0 15d certified-operators-5fhz4 1/1 Running 0 7h30m community-operators-kftpt 1/1 Running 0 1h8m marketplace-operator-6cc74874c7-kz89g 1/1 Running 0 141d redhat-marketplace-72k4h 1/1 Running 0 5d redhat-operators-d7frj 1/1 Running 0 16h Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: