Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Synchroznization of product with two repos (having same source and holding some distributions) sometimes ends up with error
E11000 duplicate key error index: pulp_database.distribution.$_id_  dup key: { : "ks-Test Family-TestVariant-16-x86_64" }

Unfortunately this doesn't happen always. It looks like a race condition.


Version-Release number of selected component (if applicable):
pulp-1.0.0-5
katello-0.2.14-1


Steps to Reproduce:
1. create a product
2. add two repositories with the same source that hold some distro (eg. http://tstrachota.fedorapeople.org/dummy_repos/zoo/)
3. try to sync the product

Tomas, I assume this still happens and we can reproduce the problem?

Is there any fallout due to the log message?  
 1. It's not clear from your report ... does the sync fail?  
 2. If sync succeeds, are the synced repositories unusable?

If any of the above are TRUE, please set the 'cloudforms-1.0.0' and 'blocker' flags to '?'

If the problem is only a log message, please set the 'cloudforms-1.1.0' flags to '?'

Thanks!

Sorry for not being specific.

From my observation the sync fails only for one of the repositories. As they have the same source, the packages are available in Library at the end. Therefore I don't think this is a blocker. I also assume that having the same repos in one product is rather rare usecase.

moving to 1.1

I am not able to reproduce this issue, and with the pending Pulp V2 integration upstream we can re-visit if this is found again.