-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oadm prune is pruning layers referenced by other images #14863
Comments
Was the image sha256:112edbdddc113654404d039fcb2984834834f385720d1f43f89266e6d1532bf5 pushed concurrently with the pruning? |
@dmage I don't have the exact timestamp from that prune anymore, but it seems likely that it did. Our pruning job runs at |
Although saying that image |
@soltysh have you seen such a problem before? |
@aliscott can you provide the exact commands to reproduce this? |
@dmage I don't have a way of reproducing it 100% of the time, but I have seen it a couple of times now. We have a job that runs this every hour:
|
Any update on this? |
It seems we have problems with keep-younger-than. No estimations, though. |
Thanks for the update @dmage, so is |
@dmage |
@aliscott @alikhajeh1 Yes - Two images referenced Layer X: Image A -> Layer X oc adm prune Runs: Image A is valid prunable Result: |
@mrobson thanks for the confirmation! We've just found the problem: https://github.com/openshift/origin/pull/16580/files#r141612326 |
Automatic merge from submit-queue (batch tested with PRs 16644, 16649, 16656, 16651, 16663). Pruning should keep layers referenced by other images Fixes #14863 [BZ 1487408](https://bugzilla.redhat.com/show_bug.cgi?id=1487408)
Version
The image pruner is pruning layers from the registry that are referenced by other images. This is causing my deployment configs to fail with image back offs. When pulling the latest image I get an
unknown blob
error.Here is the output after I had run
oc adm prune images --keep-tag-revisions=5 --keep-younger-than=48h --confirm
Output of docker pull for the latest sha:
Notice how it can't pull layer
efaa9adc05c0
which had been pruned above.Additional Information
Here is the output of
oc get is alistair-test -o yaml
The text was updated successfully, but these errors were encountered: