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:
On a FIPS enabled system, I was able to sync md5 and sha1 repos successfully.  I was also able to publish those repos on a cv successfully as well, but it threw errors in the logs.

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

How reproducible:


Steps to Reproduce:
1. On a 6.9 satellite box, enabled FIPS following the instructions on https://access.redhat.com/solutions/137833
2. Sync rhel6, rhel7, rhel8 repos
3. Create a custom yum repo and sync https://fixtures.pulpproject.org/rpm-with-md5/ & https://fixtures.pulpproject.org/rpm-with-sha-1-modular/ for sha1 and md5
4. Create a content view and add the repos from 2 and 3.
5. Publish content view
6. Check /var/log/messages

Actual results:
log contains errors.

Expected results:
Should see no errors in log.

Additional info:

This is a pulp2 issue.
Looking at the code, it looks like an old issue. I expect it to exist in all previous Sat versions.

Lai, could you share the resulted repomd.xml for the md5 and sha1 repositories?
I'd like to check the its correctness.

Thanks.

Since this issue will be fixed upon upgrade to Satellite 6.10 (repomd.xml file is incomplete for md5 repo but migration to Satellite 6.10 will regenerate the repo metadata correctly,) we won't plan to fix this in 6.9.z. This has not been reported by any customers so it's likely customers using FIPS aren't syncing md5 repos.