Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1399065 - [RFE] /var/lib/pulp growing on satellite
Summary: [RFE] /var/lib/pulp growing on satellite
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.10
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 08:36 UTC by Vladimir Dulava
Modified: 2020-02-14 18:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-27 13:26:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimir Dulava 2016-11-28 08:36:12 UTC 
Description of problem:
/var/lib/pulp on our satellite server keeps growing.  This is where the synced rpms from Redhat are. Customer wants to have some way to purge old or unused rpms on a regular schedule to manage the growth of this filesystem.

Version-Release number of selected component (if applicable):
Sat 6

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Customer wants the synced repository not to contain old version of packages and requested this RFE to be open.
Comment 1 Michael Hrivnak 2016-12-12 19:48:02 UTC 
Pulp has a feature that does this for RPMs, and is an optional setting on the yum importer. See "retain_old_count" here: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/yum-plugins.html#yum-importer

Katello would need to expose that option.

For any other similar functionality, for example with other data types, the user must be given the opportunity to choose what kind of pruning should happen. Pulp's default is to retain content by default, which is an important guarantee.

I'm moving this to the "Content Management" component, so that katello can evaluate any other desired pruning scenarios, and make pulp RFEs as required.
Comment 2 Brad Buckingham 2017-01-05 01:18:03 UTC 
In Satellite 6.2, there are a couple of features that may be set on repositories that may be useful in managing space:

1. 'Mirror on Sync':  With this feature, each time a repository is synchronized, if a new version of a package is downloaded, the old version is removed.

2. 'On Demand' (Download Policy):  With this feature, the content will only get downloaded to the filesystem when a client requests it.

Would either of these features address the customers needs?
Note You need to log in before you can comment on or make changes to this bug.