Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionTanya Tereshchenko
2017-04-18 18:48:38 UTC
Description of problem:
When multiple repositories of the similar errata content is synced in parallel, race condition can happen during import of errata. Most likely this issue will be observed on a Capsule.
In the Pulp task report one can observe the following error:
"errata"=> {"state"=>"FAILED",
"error"=> "Tried to save duplicate unique keys (insertDocument :: caused by :: 11000 E11000 duplicate key error index: pulp_database.units_erratum.$errata_id_1 dup key: { : \"RHSA-2017:0907\" })"}
Comment 1pulp-infra@redhat.com
2017-04-18 19:02:40 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 2pulp-infra@redhat.com
2017-04-18 19:02:42 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2017-04-18 20:02:29 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2017-04-18 20:32:41 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 6pulp-infra@redhat.com
2017-05-17 13:33:59 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2017-05-24 18:34:17 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2466
Description of problem: When multiple repositories of the similar errata content is synced in parallel, race condition can happen during import of errata. Most likely this issue will be observed on a Capsule. In the Pulp task report one can observe the following error: "errata"=> {"state"=>"FAILED", "error"=> "Tried to save duplicate unique keys (insertDocument :: caused by :: 11000 E11000 duplicate key error index: pulp_database.units_erratum.$errata_id_1 dup key: { : \"RHSA-2017:0907\" })"}