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.
Bug 1985958 - [pulp3] Sync fails for repositories with duplicated content by checksum or by path
Summary: [pulp3] Sync fails for repositories with duplicated content by checksum or by...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-26 11:11 UTC by Tanya Tereshchenko
Modified: 2021-11-16 14:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1992274 (view as bug list)
Environment:
Last Closed: 2021-11-16 14:12:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 7208 0 Normal CLOSED - CURRENTRELEASE Error during sync : Path is duplicated 2021-08-27 16:12:39 UTC
Pulp Redmine 8133 0 Normal CLOSED - CURRENTRELEASE Same package from different repos yields error on sync 2021-08-26 13:16:53 UTC
Pulp Redmine 9192 0 Normal CLOSED - CURRENTRELEASE Backport #7208 "Error during sync : Path is duplicated" to 3.14.z 2021-10-12 14:08:29 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:13:03 UTC

Description Tanya Tereshchenko 2021-07-26 11:11:20 UTC 
Description of problem:
Pulp 3 currently doesn't handle well the following situations:
 - 2 packages with the same NEVRA, same checksum but different filenames/location
      - e.g. https://packages.grafana.com/oss/rpm
          - grafana-2.6.0-1.x86_64.rpm
          - grafana-2.6.0.x86_64.rpm

      - it can be just 2 different repositories having the same package under different paths

 - 2 packages with the same NEVRA, different checksums, same filenames but in different location/directory
      - e.g. http://ftp.cs.stanford.edu/centos/7/opstools/x86_64/
          - fluentd/rubygem-multipart-post-doc-2.0.0-2.el7.noarch.rpm
hash 6a8148297b09c9bb7fa433e1559e20760b21c6d9cf10eb8569e053704b20d8c9
          - logging/rubygem-multipart-post-doc-2.0.0-2.el7.noarch.rpm
hash 48e054113e7bb6b4b52d9c34726f5a58ccdc8045bfe5e15f687306ef935f49d3


It's a regression in comparison to pulp2 which just picks one.

Version-Release number of selected component (if applicable):
pulp_rpm 3.14.0 and older


How reproducible:
Always


Steps to Reproduce:
Sync repositories from the description, and observe errors.


Actual results:
There are 2 different errors but they are related.
They can't be fixed/tested separately.

You get either
`Cannot create repository version. Path is duplicated: <duplicated RPM>.`
or
`ValueError: No declared artifact with relative path X for content "<Package: Y>"`

Expected results:
Pick one and log warnings about duplicated or overlapped paths.
Comment 1 pulp-infra@redhat.com 2021-07-26 18:10:04 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 2 pulp-infra@redhat.com 2021-07-26 18:10:06 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2021-07-26 18:10:27 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2021-07-26 18:10:29 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2021-07-28 20:09:03 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2021-08-09 17:17:21 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2021-08-09 17:17:41 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 16 pulp-infra@redhat.com 2021-08-26 13:16:54 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 17 pulp-infra@redhat.com 2021-08-27 16:12:40 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 18 pulp-infra@redhat.com 2021-10-12 14:08:30 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 19 pulp-infra@redhat.com 2021-10-12 14:08:31 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 22 errata-xmlrpc 2021-11-16 14:12:52 UTC 
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702
Note You need to log in before you can comment on or make changes to this bug.