I accidently reproduced the issue[0]. We should now be able to fix it. [0] https://pulp.plan.io/issues/6463#note-5
On Mon, Apr 20, 2020 at 11:25 AM Dennis Kliban <[email protected]> wrote: > The issue does not have any steps to reproduce it. Have you been able to > consistently reproduce the issue with a specific repository? Does it go > away the next time you perform the sync? > > On Wed, Apr 8, 2020 at 9:03 AM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> Thanks Brian. I filed an issue https://pulp.plan.io/issues/6463 >> >> From: [email protected] At: 04/07/20 15:59:11 >> To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> >> Cc: [email protected] >> Subject: Re: [Pulp-list] pulp 3.2.1 duplicate key error >> >> I heard another developer report a similar issue, but we couldn't >> reproduce it. Could you file this as an issue also please? >> >> On Tue, Apr 7, 2020 at 3:42 PM Bin Li (BLOOMBERG/ 120 PARK) < >> [email protected]> wrote: >> >>> Noticed we have a few errors when running sync. >>> >>> "error": { >>> "description": "duplicate key value violates unique constraint >>> \"core_repositoryversion_repository_id_number_3c54ce50_uniq\"\nDETAIL: Key >>> (repository_id, number)=(59eb02b1-edab-46e3-a69b-d69a8b314f20, 2) already >>> exists.\n", >>> >>> What could be the cause of this? How can we resolve it? >>> _______________________________________________ >>> Pulp-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-list >> >> >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list > >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
