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.

Description of problem:
Exported tarball containing multiple repositories, when importing may fail if a package belongs to more than one repository.

Version-Release number of selected component (if applicable):


How reproducible:
All the time at customer's environment

Steps to Reproduce:
1. Sync 2 repositories that may contain the same package. Example:

Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server
Red_Hat_Software_Collections_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server

2. Export the entire library

3. On another satellite, import the tarball generated by the export on item 2

Actual results:

Import task fails complaining about duplicate entries:


Expected results:

Import would ignore duplicates and finish successfully.

Additional info:

This bug was fixed in pulpcore 3.16.5, 3.17.5, and 3.18.0.

It's also available as far back as pulpcore 3.14.13 so it should be pulled into Sat 6.10 also.

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.11 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-2022:5498