Bug #17610

CV Publish failing for combination of repos

Added by Partha Aji over 4 years ago. Updated almost 3 years ago.

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


  • Create a new COntent view
  • Add a yum repo + ostree repo or yum repo and a file repo or a yum repo and docker repo
  • Publish the CV

Publish properly working

Publish fails in the CopyRpm phase with a comment

 data: {}
 description: The target importer does not support the types from the source
 sub_errors: []

What you also note is that CopyRpm call is getting run on ostree/file repos

source_pulp_id: Default_Organization-yawn-ostree
target_pulp_id: Default_Organization-future-1_0-wow-partello
remote_user: admin
remote_cp_user: admin
locale: en

While CopyOstreeBranch needs to be running.

This bug is related to this change ->

Basically the CloneToVersion treats a bunch of repositories as the same type. This means in a cv with yum and docker repos, Docker repos may get copied to yum repos which wil cause th eabove failure

Associated revisions

Revision 648336c3 (diff)
Added by Partha Aji over 4 years ago

Fixes #17610 - Corrects multi repo cv publishes

Commit e5586b7e6bfd07455997fdb1d7651650f9a83154 broke publishing of
non-composite content views with multiple repositories. This is because
the changes were meant more for composite cv's and assumed library
instances of repositories to be published to be non nil.
In short you could not add a yum repo and repo of another type and
publish em together.
This commit fixes that issue by treating repos with no library
instances differently from ones with library instances (which tend to
be the component cv repos.)


#1 Updated by Partha Aji over 4 years ago

  • Assignee changed from Brad Buckingham to Partha Aji

#2 Updated by The Foreman Bot over 4 years ago

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

#3 Updated by Justin Sherrill over 4 years ago

  • Legacy Backlogs Release (now unused) set to 188

#4 Updated by Partha Aji over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF