Bug #24841
closed
Forcing content view version repository regeneration does not actually regenerate some repositories
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1626294
Description of problem:
The force/force_full option is not properly used on some repositories (those that use the yum_clone_distributor), and pulp takes this option into consideration for all distributors.
Version-Release number of selected component (if applicable):
6.3.3
How reproducible:
Always
Steps to Reproduce:
1. Create a content view, add a repo 'foo', publish it
2. Look at the timestamps in /var/lib/pulp/published/yum/master/yum_distributor/*CV_LABEL*ENV_LABEL*/TIMESTAMP/repodata/
3. Regenerate the repodata from the content > content views > click your view > click "regenerate repository Metadata" in the actions dropdown beside the version you just published.
Actual results:
metadata is not regenerated, timestamps are not updated
Expected results:
metadata is regenerated
Additional info:
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Justin Sherrill
- Pull request https://github.com/Katello/katello/pull/7684 added
Updated by Justin Sherrill over 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|c2194967d34aee59ced6bc25918f8e9d9e198d87.
Updated by Jonathon Turel over 6 years ago
- Category changed from 111 to Content Views
- Target version set to Katello 3.8.1
- Triaged changed from No to Yes
Updated by Justin Sherrill about 6 years ago
- Target version changed from Katello 3.8.1 to Katello 3.9.0