Thanks! That's a very nice patch, after trying for a week to get the migration to work and continously searching for and deleting duplicate pulp2 content, the migration worked right away after this patch. :)
Or, at least regarding the duplicate content errors, however I still have problems with a createrepo_c error, same as described in https://pulp.plan.io/issues/7193 (huge input lookup). That error only arise for a few packages so that is manageable for me to purge from pulp2 before migration, but it would be nice to not have to do that.. //Adam ________________________________ From: Dennis Kliban <[email protected]> Sent: 27 September 2020 17:35 To: Winberg Adam Cc: Ina Panova; [email protected] Subject: Re: [Pulp-list] 2to3migration fails on 'Package' object has no attribute '_remote_artifact_saver_cas' Here is a patch for pulpcore that fixes this problem[0]. [0] https://github.com/pulp/pulpcore/pull/937 On Mon, Sep 21, 2020 at 7:17 AM Winberg Adam <[email protected]<mailto:[email protected]>> wrote: Thank you for your reply - yes I did clean orphans after i removed the pulp2 repos that i suspected might be the cause. But as you say, there might be some other cause for this in my case. At the moment I have adjusted the code so the iteration only runs if the '_remote_artifact_saver_cas' attribute is present. Don't know if the result will be any good though, running the migration right now. //Adam ________________________________ From: Ina Panova <[email protected]<mailto:[email protected]>> Sent: 21 September 2020 13:09 To: Winberg Adam Cc: [email protected]<mailto:[email protected]> Subject: Re: [Pulp-list] 2to3migration fails on 'Package' object has no attribute '_remote_artifact_saver_cas' Hi, the provided steps in the mentioned issue are the steps to reproduce the issue, however, unfortunately, this does not necessarily mean that this is the root cause of the manifested problem. Apparently we need to find a fix to properly handle duplicated declarative content in a batch. Looking at the steps you have tried to bypass the issue, have you run orphan clean up after pulp2 repos removal? -------- Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Sun, Sep 20, 2020 at 9:05 AM Winberg Adam <[email protected]<mailto:[email protected]>> wrote: Hi, When running the 2to3migration for the 'rpm' plugin, I get the following error: AttributeError: 'Package' object has no attribute '_remote_artifact_saver_cas' This is the same as specified in https://pulp.plan.io/issues/7147, and I actually had a couple of repos in pulp2 which shared the same feed. I removed the redundant repos, flushed the pulp3 db and reran the 2to3-migration but still got stuck on the same error. Anyone got any pointers how to resolve this? //Adam _______________________________________________ Pulp-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
