Project

General

Profile

Actions

Bug #26422

closed

Distributor publish happening even if "matching_content" is true

Added by Partha Aji almost 6 years ago. Updated almost 6 years ago.

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

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 #1

Updated by Andrew Kofink almost 6 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Samir Jha
  • Pull request https://github.com/Katello/katello/pull/8074 added
Actions #3

Updated by Anonymous almost 6 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF