Verified on 4.2.0-0.nightly-2019-10-27-140004: $ oc project openshift-image-registry Now using project "openshift-image-registry" on server "https://api.qe-hongli-42bv.qe.devcluster.openshift.com:6443". [wzheng@openshift-qe 4.1.z]$ oc exec image-registry-6bff7f877-qqws4 -- /bin/sh -c 'REGISTRY_LOG_LEVEL=info /usr/bin/dockerregistry -prune=check' time="2019-10-28T09:35:29.151275389Z" level=info msg="start prune (dry-run mode)" distribution_version=v2.6.0+unknown go.version=go1.11.13 openshift_version=v4.2.2-201910251319+15ab28d-dirty time="2019-10-28T09:35:29.527774814Z" level=info msg="Invalid image name foo/test/ruby-ex, removing whole repository" go.version=go1.11.13 time="2019-10-28T09:35:29.685653349Z" level=info msg="The image stream wsuvl/sti is not found, will remove the whole repository" go.version=go1.11.13 time="2019-10-28T09:35:29.685688495Z" level=info msg="Would delete repository: foo/test/ruby-ex" go.version=go1.11.13 time="2019-10-28T09:35:29.820217318Z" level=info msg="Would delete repository: wsuvl/sti" go.version=go1.11.13 Would delete 0 blobs Would free up 0B of disk space Use -prune=delete to actually delete the data
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-2019:3303