1. Proposed title of this feature request - Recover space of old container image versions 2. Who is the customer behind the request? Account: name and acct # <- please include both TAM customer: yes CSM customer: no Strategic: yes 3. What is the nature and description of the request? - recover space of old container image versions, that are stored within custom repositories, assigned to content-views, managed systems are registered to. 4. Why does the customer need this? (List the business requirements here) - He needs a lot of time synchronizing content 5. How would the customer like to achieve this? (List the functional requirements here) - A feature that helps to delete old images and free space 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? - no 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? - RHEL 7 9. Is the sales team involved in this request and do they have any additional input? - no 10. List any affected packages or components. (I'm not a satellite specialist - I would like to ask the customer for more infos if needed) - Docker - Content Management from Satellite 11. Would the customer be able to assist in testing this functionality if implemented? - yes
The problem is that using containers fills up the Satellite quite fast. Using 200 containers fills up with 22K mainfests and 15K image tags ... Something like "keep only actual version + former version" would be great. Everything could be automatically purged or reloaded if necessary and deleted after XX days, if not needed any more
Update: i played around with the new Option to delete content in Satellite 6.5. I started with the openshift3/ose Container which consists of 583 "Container Image Manifests", 80 "Container Image Manifest Lists" and 338 "Container Image Tags". I selected abou 140+ Image Manifests showing versions of OSE 3.1 - 3.10 ( we run 3.11 so this stuff is obsolete in my opinion ). I was able to remove these Manifests but it didnt deleted anything from the disc, even after letting the pulp-maintenance script run. I selected this particular container to resync with Red Hat ... and voila ... all manual deleted content was resynced ... Creating a new CV now takes 2 hours 10 minutes .... container obsoletes fill up 80% of our satellite space.
This is likely a duplicate of this bug here which we are tracking upstream in Pulp as well: https://bugzilla.redhat.com/show_bug.cgi?id=1690070 will confirm and unify on the bug above if so.
Yes Mike, you can unify both. Thanks for point that! All the best, Gabriel
Hi, mentioned 2nd bug was fixed and performance of operations got better with Sat 6.6 ... but my request still exists in getting rid of the old blobs ... Any ideas in optimizing this storage behaviour ?
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Created redmine issue http://projects.theforeman.org/issues/31782 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31782 has been resolved.
Verified: Version Tested: Satellite 6.10.0 snap 23 Steps Followed: 1. Have an upstream repository with some items in it 2. Change the upstream repository 3. Confirm the changes are mirrored when the repository is synced with upstream Observation: The changes are mirrored when the repository is synced with upstream
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702