Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1085087 +++
Description of problem:
Currently in pulp packages are re-downloaded every time they need to be pulled down per-repository. If they already exist on the file system the existing file is not reused (after being validates to have the correct checksum)
We are under the impression this used to work in a previous version of pulp.
It is very advantageous to have this behavior as within katello:
* multiple orgs may sync the same repo resulting in multiple repositories within pulp. A new org syncing the same repo should be much faster.
* During testing we can leave the contents of /var/lib/pulp/content alone and be able to sync repositories much much quicker after the initial sync.
Version-Release number of selected component (if applicable):
2.3
How reproducible:
Always
Steps to Reproduce:
1. Create a Repo pointing to a very large upstream repo
2. Sync the repo
3. Create another repo pointing to the same very large upstream repo
4. Sync the 2nd repo
Actual results:
All packages are re-downloaded
Expected results:
All packages should not be re-downloaded since they already exist on the file system.
Synced as suggested the rhel65 repo 2 times with different names, but we see the size with that of only 1 repo.
/var/lib/pulp/content
[root@xxxx content]# du -sh ./*
473M ./distribution
3.7G ./rpm
20K ./yum_repo_metadata_file