Red Hat Bugzilla – Bug 1355752
content view publish may fail if 'publish via http' was changed to false on a repo
Last modified: 2017-10-02 05:35:56 EDT
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.
Created from redmine issue http://projects.theforeman.org/issues/15649
Upstream bug assigned to jsherril@redhat.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/15649 has been closed
*** Bug 1222367 has been marked as a duplicate of this bug. ***
*** Bug 1219558 has been marked as a duplicate of this bug. ***
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