https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-01-21T16:28:49ZPulpPulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=666192021-01-21T16:28:49Zdalleydalley@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-11 priority-6 priority-default closed" href="/issues/7208">Issue #7208</a>: Error during sync : Path is duplicated</i> added</li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=666202021-01-21T16:30:19Zdalleydalley@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=666222021-01-21T16:33:56Zdalleydalley@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-12 priority-6 priority-default closed" href="/issues/7507">Issue #7507</a>: Pulp RPM 3.6.2 - ValueError: Cannot create repository version. Path is duplicated</i> added</li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=670442021-02-03T09:29:07Zadam.winberg@smhi.se
<ul></ul><p>After a thorough cleaning - removing the offending package, deleting all repoversions where it was present and deleting orphans - I can no longer reproduce this error. I suspect there was something in the metadata from my pulp2 migration that caused this.</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=718892021-06-14T09:28:17Zgvde
<ul></ul><p>I still have the same problem. It's been discussed here: <a href="https://community.theforeman.org/t/foreman-2-4-katello-4-unable-to-sync-repos/23646" class="external">https://community.theforeman.org/t/foreman-2-4-katello-4-unable-to-sync-repos/23646</a></p>
<p>Possibly related with multiple rpms having the identical checksum?</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=725542021-06-29T08:24:34Ztrendyandy
<ul></ul><p>I have the same issue with syncing postgresql and grafana. What can we do to bring this forward?</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=729412021-07-08T14:13:12Zjsherril@redhat.comjsherril@redhat.com
<ul><li><strong>Tags</strong> <i>Katello</i> added</li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=733582021-07-16T15:19:16Zmartin
<ul></ul><p>trendyandy wrote:</p>
<blockquote>
<p>I have the same issue with syncing postgresql and grafana. What can we do to bring this forward?</p>
</blockquote>
<p>we are impacted by this, also with Grafana repo</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=735592021-07-21T19:41:27Ziballou
<ul></ul><p>Especially for Katello users in this thread, it would be good to know if Pulpcore 3.14 helps out with this issue. Katello 4.1 is now on Pulpcore 3.14 (and related plugins).</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=735642021-07-21T19:52:35Zgvde
<ul></ul><p>Briefly checked: on 4.1.1 with pulpcore 3.14. grafana sync this morning:</p>
<p>No declared artifact with relative path "grafana-2.6.0.x86_64.rpm" for content "<Package: grafana>"</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=735892021-07-22T05:20:00Zgvde
<ul></ul><p>For PostgreSQL it seems the repository changed: the repo file rpms are now at <a href="https://download.postgresql.org/pub/repos/yum/reporpms/" class="external">https://download.postgresql.org/pub/repos/yum/reporpms/</a> and not in the general repositories anymore. So there is no problem anymore.</p>
<p>Currently, I see it with grafana and also with eduvpn:</p>
<p><a href="https://repo.letsconnect-vpn.org/2/rpm/epel-7-x86_64/" class="external">https://repo.letsconnect-vpn.org/2/rpm/epel-7-x86_64/</a></p>
<pre><code>Cannot create repository version. Path is duplicated: php-fkooman-secookie-5.0.2-1.el7.noarch.rpm.
</code></pre> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=736402021-07-22T20:20:18Zggainey
<ul><li><strong>Project</strong> changed from <i>RPM Support</i> to <i>Pulp</i></li></ul><p>The fix for this particular failure-scenario is in artifact_stages in pulpcore. Switching to the correct project.</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=736412021-07-22T20:23:42Zpulpbot
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>POST</i></li></ul><p>PR: <a href="https://github.com/pulp/pulpcore/pull/1513" class="external">https://github.com/pulp/pulpcore/pull/1513</a></p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=736432021-07-22T20:50:00Zdalleydalley@redhat.com
<ul><li><strong>Assignee</strong> set to <i>ggainey</i></li><li><strong>Sprint/Milestone</strong> set to <i>3.15.0</i></li><li><strong>Sprint</strong> set to <i>Sprint 101</i></li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=736442021-07-22T20:51:21Zdalleydalley@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-1 status-11 priority-6 priority-default closed" href="/issues/9130">Issue #9130</a>: Backport #8133 "Same package from different repos yields error on sync" to 3.14.z</i> added</li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=740992021-08-02T17:44:45Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Sprint</strong> changed from <i>Sprint 101</i> to <i>Sprint 102</i></li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=743062021-08-09T16:22:28Zggainey
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="Loosens the constraints around what can be in a new-repository-version. There are RPM repositori..." href="https://pulp.plan.io/projects/pulp/repository/pulpcore/revisions/349f2137d970f87190749b417cfa137dc0f99ff5">pulpcore|349f2137d970f87190749b417cfa137dc0f99ff5</a>.</p> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=743762021-08-10T19:35:11Zttereshcttereshc@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-7 status-11 priority-6 priority-default closed" href="/issues/9227">Backport #9227</a>: Backport #8133 "Same package from different repos yields error on sync" to 3.7.z</i> added</li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=748622021-08-26T12:35:45Zpulpbot
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #8133: Same package from different repos yields error on synchttps://pulp.plan.io/issues/8133?journal_id=759822021-09-24T13:54:53Zjsherril@redhat.comjsherril@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-7 status-9 priority-6 priority-default closed" href="/issues/9446">Backport #9446</a>: Backport #8133 "Same package from different repos yields error on sync" to 3.9.z</i> added</li></ul>