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:
Re-sign a rpm that is already existed in the repository and re-upload it to the Satellite repository causes duplicate rpms in the Web UI.

Steps to Reproduce:
1. Buld or prepare an unsigned rpm.
2. Create a gpg key.
3. Use the gpg key to sign the rpm with sha1.
4. Create a rpm repository in the Satellite.
5. Upload the sha1 signed rpm to the repository.
6. Use the gpg key to re-sign the rpm with sha2 again.
7. Upload the sha2 signed rpm to the repository.

Actual results:
Web UI shows that the repository contains duplicate rpms

Expected results:
No duplicate rpms show in the Web UI

Additional info:
Reindex the repository fixes the issue

echo '
  Katello::Repository.find(<REPLACE THIS WITH THE REPO ID>).index_content
' | foreman-rake console

Created redmine issue https://projects.theforeman.org/issues/31455 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31455 has been resolved.

Verified on 6.9.0 snap 11.0.

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.9 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:1313