Project

General

Profile

Bug #26422

Distributor publish happening even if "matching_content" is true

Added by Partha Aji about 3 years ago. Updated about 3 years ago.

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

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.

Associated revisions

Revision 6ebf1e36 (diff)
Added by sjha4 about 3 years ago

Fixes #26422 - Matching content not considered before publish

History

#1 Updated by Andrew Kofink about 3 years ago

  • Triaged changed from No to Yes

#2 Updated by The Foreman Bot about 3 years ago

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

#3 Updated by Anonymous about 3 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF