Actions
Bug #26422
closedDistributor publish happening even if "matching_content" is true
Description
During a content view publish katello checks if anything changed between the source and destination repos. If nothing changed the metadata should not get regenerated. This is not the case in the upstream nightly. It does not seem to care about the matching_content flag while checking for a distributor publish.
1) Create and a sync a repo
2) Create a content view and add the repo
3) Publish the cv
4) Pubish the cv again
5) Go to the dynflow console for the 2nd publish task
Check the output of
Actions::Pulp::Repository::DistributorPublish
Expected:
matching_content_skip: true
Actual:
No skip, instead its a full blown distributor publish.
Actions