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.
Description of problem:
There seems to be missing metadata fields within the repodmd.xml for MD5. At the moment, it only contains "group" data type in the repodmd.xml file.
Version-Release number of selected component (if applicable):
6.9.7 snap 3
How reproducible:
100%
Steps to reproduce
1. On a 6.9.7 satellite box, enabled FIPS following the instructions on https://access.redhat.com/solutions/137833
2. 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
3. In the repos details page, click the "published at" link and drill into the repodata and repomd.xml file
Actual results:
repomd.xml file only has the "group" data type within the file.
Expected results:
The repomd.xml should have 'primary', 'filelists` and `updateinfo`.
Additional info:
I have only seen this with MD5 Repos. I have not looked if it's also impacting SHA1, SHA256, or any of the rhel6,7,8 repos yet. I would leave the investigation up to dev.
Hello, checked on Satellite 6.9.9 snap1 (python3-pulp-rpm-3.11.4-1.el7pc.noarch), the repomd.xml problem persists when syncing https://fixtures.pulpproject.org/rpm-with-md5/ to a fips-enabled satellite. The synced repomd.xml looks as follows
<repomd>
<revision>1648117368</revision>
<data type="group">
<location href="repodata/e909ddae328b9f59c3f3b3fdaad8acbe-comps.xml"/>
<timestamp>1648117368</timestamp>
<size>2357</size>
<checksum type="md5">e909ddae328b9f59c3f3b3fdaad8acbe</checksum>
</data>
</repomd>
Journalctl exhibits the exact same error as mentioned in comment 3
Reproducer machine available upon ping.
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 (Important: Satellite 6.9.9 Async Bug Fix Update), 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:1478