Project

General

Profile

Actions

Bug #15649

closed

conflict with dangling repo symlink and yum_clone_distributor

Added by Justin Sherrill over 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 2 (0 open2 closed)

Has duplicate Katello - Bug #16268: Content View: UI: publishing version does not update the Content View list detailsDuplicateWalden Raines08/24/2016Actions
Has duplicate Katello - Bug #16266: publishing content view after I have made repository available through HTTPS only fails: PLP0000: Failed to copy metadata.Duplicate08/24/2016Actions
Actions #1

Updated by Justin Sherrill over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/pulp-katello/pull/20 added
Actions #2

Updated by Justin Sherrill over 7 years ago

  • Bugzilla link set to 1355752
Actions #3

Updated by Justin Sherrill over 7 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.

Actions #4

Updated by Justin Sherrill over 7 years ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Justin Sherrill over 7 years ago

  • Has duplicate Bug #16268: Content View: UI: publishing version does not update the Content View list details added
Actions #6

Updated by Brad Buckingham over 7 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
Actions

Also available in: Atom PDF