+++ This bug was initially created as a clone of Bug #1806686 +++ Description of problem: If the image pruner has been installed, and then the image registry is marked `Removed`, the image pruner CronJob and other components are also removed. Version-Release number of selected component (if applicable): 4.4.0 How reproducible: Always Steps to Reproduce: 0. Ensure the image registry is installed and the operator is `Managed` 1. Configure the image pruner for the cluster. 2. Mark the image registry as `Removed` Actual results: Image pruner CronJob and other components are removed. Expected results: Image pruner CronJob remains, and is upgraded to only prune image metadata in etcd.
*** Bug 1807363 has been marked as a duplicate of this bug. ***
Verified on 4.4.0-0.nightly-2020-02-26-185356: $ oc get pods NAME READY STATUS RESTARTS AGE cluster-image-registry-operator-7d88768b6d-6gbfl 2/2 Running 0 3h16m image-pruner-1582773600-gd256 0/1 Completed 0 112s image-pruner-1582773660-542j5 0/1 Completed 0 102s image-pruner-1582773720-mztkq 0/1 Completed 0 42s node-ca-5z89r 1/1 Running 0 3h16m node-ca-8cbbx 1/1 Running 0 3h12m node-ca-bpg7t 1/1 Running 0 3h12m node-ca-dxj68 1/1 Running 0 3h12m node-ca-n6ztv 1/1 Running 0 3h16m node-ca-skmw2 1/1 Running 0 3h16m
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:0581