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:
When syncing puppet repositories to a capsule through a content view there is no content available in the folder path on the capsule for that puppet repository. When syncing a puppet module that is part of a repository in Library to a capsule, the puppet module is in the correct location on the capsule.
For example:
On the capsule, I see the puppet module for the Library repository
/var/lib/pulp/published/puppet/https/repos/Default_Organization-puppet_pro-puppet_repo/system/releases/o/openstack/openstack-nova-7.0.0.tar.gz
but (still on the capsule) when I check for the puppet module for the content view, it is not there.
/var/lib/pulp/published/puppet/https/repos/Default_Organization-Library-puppet_cv/
Version-Release number of selected component (if applicable):
How reproducible:
%100
Steps to Reproduce:
1.Upload a puppet module to a repository
2.Create a content view in Library with that puppet module
3.Sync a capsule with Library environment
4.Check for puppet module content in /var/lib/pulp/published/puppet/https/repos/<content view directory>/
Actual results:
No puppet module exists in the correct file location on a capsule
Expected results:
The content exists in the correct location
Additional info:
Verified !
@ Sat 6.2 Snap 18.1 GA
On syncing capsule, the puppet module is copied to published/promoted CV folder in capsule.
# ll /var/lib/pulp/published/puppet/https/repos/Default_Organization-Dev-puppet_cv/system/releases/j/jfryman/jfryman-selinux-0.3.1.tar.gz
-> lrwxrwxrwx. 1 apache apache 136 Jul 1 06:57 /var/lib/pulp/published/puppet/https/repos/Default_Organization-Dev-puppet_cv/system/releases/j/jfryman/jfryman-selinux-0.3.1.tar.gz -> /var/lib/pulp/content/units/puppet_module/46/1f06507db135e9342f5a2a77721fa22a94c39d855e639efc1740cafc1053f5/jfryman-selinux-0.3.1.tar.gz
So moving this bz to Verified !
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, 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/RHBA-2016:1501