Bug #15649
closed
conflict with dangling repo symlink and yum_clone_distributor
Description
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.
Updated by Justin Sherrill over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/pulp-katello/pull/20 added
Updated by Justin Sherrill over 8 years ago
Note you can 'fix' the problem by finding the broken symlinks:
find /var/lib/pulp/published/yum/http -type l -exec sh -c "file -b {} | grep -q ^broken" \; -print
and deleting them.
Updated by Justin Sherrill over 8 years ago
- Status changed from Ready For Testing to Closed
Updated by Justin Sherrill about 8 years ago
- Has duplicate Bug #16268: Content View: UI: publishing version does not update the Content View list details added
Updated by Brad Buckingham about 8 years ago
- Has duplicate Bug #16266: publishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata. added