Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionTanya 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 1pulp-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 2pulp-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 3pulp-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 4pulp-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 5pulp-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 7pulp-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 8pulp-infra@redhat.com
2021-08-09 17:17:41 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 16pulp-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 17pulp-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 18pulp-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 19pulp-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.
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
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.