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.
DescriptionJustin Sherrill
2016-07-12 12:36:16 UTC
There is a conflict in the way that $SUBJECTs work together, because:
1. when setting a repo to not be published via http after it has been already been published leaves a dangling symlink
2. the yum clone distributor first starts by using the http symlink to find the path to copy its content from
We can exploit this by:
1. Create a repo with 'publish via http' set to true, url set to some upstream repo (https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/)
2. Sync the repo
3. Set 'publish via http' to false
4. Create a content view
5. Add this repo to the content view
6. Publish the content view
Your publish will fail on the yum clone distributor step.
I Verified this fix, but doing the steps Justin described above:
1. Create a repo with 'publish via http' set to true, url set to some upstream repo (https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/)
2. Sync the repo
3. Set 'publish via http' to false
4. Create a content view
5. Add this repo to the content view
6. Publish the content view
And the content view was successfully published.
Verified in Satellite 6.3 Snap 5.0
Verified in Satellite 6.2.8 Snap 2.
I followed the steps out lined in the initial bug report, and was able to publish the content view without any issues. Then I created a content view with mixed settings (some yes, some no) and was also able to publish the content views without any problems.
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-2017:0447