Bug 1467340 - [Registry][Pruning] Orphaned blobs cannot be pruned [NEEDINFO]
[Registry][Pruning] Orphaned blobs cannot be pruned
Status: CLOSED DUPLICATE of bug 1479340
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: ---
: 3.7.0
Assigned To: Michal Minar
ge liu
: Reopened
Depends On: 1408676 1499314 1499315
Blocks: 1471844 1472438
  Show dependency treegraph
Reported: 2017-07-03 08:48 EDT by Michal Minar
Modified: 2017-10-06 14:09 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1408676
: 1471844 1472438 (view as bug list)
Last Closed: 2017-08-23 10:32:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
miminar: needinfo? (mfojtik)

Attachments (Terms of Use)

  None (edit)
Comment 3 ge liu 2017-07-04 02:36:22 EDT
Verified this bug with fork ami:

openshift v1.5.0-alpha.2+c85f23e-2428
kubernetes v1.6.1+5115d708d7
etcd 3.1.0

1. add system:image-pruner role to user:
 oadm policy add-cluster-role-to-user system:image-pruner geliu

2. Run `oc adm prune images` in a loop 
 # while true; do oc adm prune images --keep-younger-than=0s --confirm; done

3. Open another terminate window and oc new-project lgp1
4. oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git
5. oc scale dc ruby-ex --replicas=0
6. Wait for build to complete

7. back to first terminate window to check the step 2, there is not any images blob be deleted

8. # docker pull successfully
9. oc delete project lgp1

10. back to first terminate window to check the step 2, there are blob data be deleted

# while true; do oc adm prune images --keep-younger-than=0s --confirm; done
Deleting registry layer blobs ...
Comment 11 Brenton Leanhardt 2017-08-23 10:32:53 EDT

*** This bug has been marked as a duplicate of bug 1479340 ***
Comment 12 Brenton Leanhardt 2017-08-23 10:36:52 EDT
Just fyi, the reason this bug targeting 3.7 was labeled a duplicate is simply because the code is already upstream in Origin which is where 3.7 is being developed.

Note You need to log in before you can comment on or make changes to this bug.