This bug was initially created as a copy of Bug #1806019 I am copying this bug because: Description of problem: If the automatic image pruner is enabled and the image registry itself is `Removed`, the image pruning jobs can fail. Version-Release number of selected component (if applicable): 4.4.0 How reproducible: Always Steps to Reproduce: 1. Create an image pruner CRD 2. Mark the internal registry as `Removed` 3. Run the image pruner Actual results: Image pruner jobs fail trying to prune images from the non-existent registry. Expected results: Image pruner jobs only prune image metadata in etcd. Additional info:
*** This bug has been marked as a duplicate of bug 1806687 ***
This is for 4.5: https://bugzilla.redhat.com/show_bug.cgi?id=1806019
For the 4.5 fix, there is one warning for image pruner when image registry is removed(https://bugzilla.redhat.com/show_bug.cgi?id=1806019#c3): $ oc logs pods/image-pruner-1583834340-ln8wn Only API objects will be removed. No modifications to the image registry will be made. Although for 4.4 image pruner no fail after image registry is removed.
If the image registry is marked as "Removed", the --prune-registry flag is removed, so this is the correct behavior.