Description of problem: If image registry is removed the pruner degrades the operator with reason ImagePrunerJobFailed::Removed Version-Release number of selected component (if applicable): 4.5.5 How reproducible: Always Steps to Reproduce: 1. Sets image registry management state as Removed 2. Wait for pruner to run Actual results: Image registry operator becomes Degraded Expected results: No degradation, as the image registry is removed we should not degrade it. Additional info: By https://bugzilla.redhat.com/show_bug.cgi?id=1806686 it seems like we still need to run the pruner so it may be useful to check why it is failing instead of changing the behavior.
Error reported by pruner pod: error: unable to determine registry: no managed image found
$ oc logs pods/image-pruner-1598412960-9sn29 error: unable to determine registry: no managed image found $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-08-25-222652 True False 60m Cluster version is 4.6.0-0.nightly-2020-08-25-222652 Waiting for a payload to include the pr.
Verified with below version: $ oc logs pods/image-pruner-1598523000-8tdq4 Only API objects will be removed. No modifications to the image registry will be made. Deleted 0 objects. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-08-26-152137 True False 10h Cluster version is 4.6.0-0.nightly-2020-08-26-152137 Status: Conditions: Last Transition Time: 2020-08-27T10:01:30Z Message: Available: The registry is removed ImagePrunerAvailable: Pruner CronJob has been created Reason: Removed Status: True Type: Available Last Transition Time: 2020-08-27T10:01:30Z Message: Progressing: All registry resources are removed Reason: Removed Status: False Type: Progressing Last Transition Time: 2020-08-26T23:29:16Z Message: Degraded: The registry is removed Reason: Removed Status: False Type: Degraded
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 (OpenShift Container Platform 4.6 GA Images), 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:4196
This comment was flagged a spam, view the edit history to see the original text if required.