Bug #25400
closedremove force_yum_metadata_regeneration method
Description
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
Updated by The Foreman Bot almost 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/7814 added
Updated by Justin Sherrill almost 6 years ago
- Blocks Tracker #24318: Pulp 3 code base prep work added
Updated by Justin Sherrill almost 6 years ago
- Target version set to Katello 3.10.0
- Triaged changed from No to Yes
Updated by Justin Sherrill almost 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|fafaf3bbebcd4c5204a99f2c9163b00955faff93.