Bug #25400

remove force_yum_metadata_regeneration method

Added by Justin Sherrill 8 months ago. Updated 8 months ago.

Content Views
Target version:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:


A long long time ago, we added an optimization that would not republish yum repo metadata when publishing or promoting a repo to a lifecycle environment. The way this works is it would compare the contents of the repo before and after the publish/promote, and if afterwards the contents did not change, it would not republish the metadata.

The purpose of this was to optimize smart proxy syncs, if the metadata doesn't change the sync will be very fast, however it introduces the possibility that we may not republish when we should be. So a force option was added to ensure the user could override this behavior.

After this, the ability to regenerate a CVV's metadata was added, which is a better method of remedying the situation since it doesn't require a user to re-publish or promote a CVV

Related issues

Blocks Katello - Tracker #24318: Pulp 3 code base prep workNew

Associated revisions

Revision fafaf3bb (diff)
Added by Justin Sherrill 8 months ago

Fixes #25400 - remove CV force metadata gen option

This removes the abiliy to ignore the optimization
for generation of yum metadata during cv publish
or promote.


#1 Updated by The Foreman Bot 8 months ago

  • Status changed from New to Ready For Testing
  • Pull request added

#2 Updated by Justin Sherrill 8 months ago

#3 Updated by Justin Sherrill 8 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.10.0

#4 Updated by Justin Sherrill 8 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF