Project

General

Profile

Bug #24841

Forcing content view version repository regeneration does not actually regenerate some repositories

Added by Justin Sherrill over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

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:

Associated revisions

Revision c2194967 (diff)
Added by Justin Sherrill over 1 year ago

Fixes #24841 - use force full with yum_clone distributor

History

#1 Updated by The Foreman Bot over 1 year ago

  • Assignee set to Justin Sherrill
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7684 added

#2 Updated by Justin Sherrill over 1 year ago

  • Status changed from Ready For Testing to Closed

#3 Updated by Jonathon Turel over 1 year ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.8.1
  • Category changed from ElasticSearch to Content Views

#4 Updated by Justin Sherrill over 1 year ago

  • Target version changed from Katello 3.8.1 to Katello 3.9.0

Also available in: Atom PDF