Hi Bin, Related to this issue, I have some questions I'm interested in. I posted them here https://pulp.plan.io/issues/6463#note-1 If you're able to post any info you have that would be great.
Thanks. Brian On Mon, Apr 20, 2020 at 7:12 PM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > We are still seeing the same errors on 8 repos out of total of 270. The > sync job failed immediately when we tried to resync. However, if we delete > and recreate the repo, we don't see the errors when we sync. > > > From: [email protected] At: 04/20/20 12:01:43 > To: [email protected] > Subject: Pulp-list Digest, Vol 125, Issue 19 > > Send Pulp-list mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/pulp-list > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pulp-list digest..." > > > Today's Topics: > > 1. Re: pulp 3.2.1 duplicate key error (Dennis Kliban) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 20 Apr 2020 11:25:42 -0400 > From: Dennis Kliban <[email protected]> > To: Bin Li <[email protected]> > Cc: pulp-list <[email protected]> > Subject: Re: [Pulp-list] pulp 3.2.1 duplicate key error > Message-ID: > <capmniups_9x_xw2nfnm2qxt_qsd-kwfuj731l7yv56cmdby...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > < > https://www.redhat.com/archives/pulp-list/attachments/20200420/6c0bc1a7/atta > chment.html> > > ------------------------------ > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > > End of Pulp-list Digest, Vol 125, Issue 19 > ****************************************** > > > _______________________________________________ > 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
