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.
+++ This bug was initially created as a clone of Bug #2161929 +++
This is a clone for Foreman Maintain, as that needs to perform the reindexing in the case of a DB restore of a EL7 backup on EL8!
+++ This bug was initially created as a clone of Bug #2142270 +++
Description of problem:
----------------------
Repository synchronization on Red Hat Satellite 6.11.3 on RHEL-8 fails with the following error :
Katello::Errors::Pulp3Error "get() returned more than one Modulemd -- it returned 2!"
Error:
Katello::Errors::Pulp3Error
get() returned more than one Modulemd -- it returned 2!
It seems to be related to the locales change in glibc-2.28 causing the collation changed in Postgresql
--------------
https://dba.stackexchange.com/questions/268027/postgresql-duplicates-despite-having-a-unique-constrainthttps://wiki.postgresql.org/wiki/Locale_data_changeshttps://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade.html
-------------
I checked 3 cases attached to this bugzilla. They are running Satellite on RHEL 8 which having glibc-2.28.
Looking at the pulp_created column in core_content, the duplicated records were also created after the release date of Satellite 6.11.
It seems like we will need to reindex all the tables to avoid the issue after upgrading the OS to RHEL 8.
--- Additional comment from on 2023-01-18T11:00:19Z
Created redmine issue https://projects.theforeman.org/issues/35966 from this bug