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.
Description of problem:
In QCI we would like the ability to mount a share with populated content (RPM/Puppet/Docker/etc) and have a means of instructing Satellite to use this content, without requiring a re-sync from a network source.
Our experience has been when we do this, Satellite will ignore the local content on the mount point and re-download the content from the network....not just metadata but all of the content will be fetched from a remote source again, defeating the time savings of using the local volume.
Use case:
1) Deploy a Satellite, configure /var/lib/pulp to be a separate EBS volume in EC2.
2) Sync 200GB of content
3) Create a snapshot the /var/lib/pulp volume
4) Deploy a new Satellite and mount the copied /var/lib/pulp volume
5) Resync content, we would like this to be a quick operation as the majority of the content already exists locally.
(In Pulp v1 we would accomplish this by just copying /var/lib/pulp and remounting it, we are asking for a similar mechanism)