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.
DescriptionVladimír Sedmík
2021-09-03 16:11:16 UTC
Description of problem:
Selected yum metadata checksum type on is not reflected in repomd.xml on a repo creation and sync. The upstream repo's checksum type is used instead, regardless the Mirror on sync settings.
Version-Release number of selected component (if applicable):
6.10.0 snap 16
How reproducible:
always
Steps to Reproduce:
1. Have a Satellite, create new Product and Repository in it with these options:
- Type: yum
- Upstream URL: https://fixtures.pulpproject.org/rpm-with-sha-512/ (for example)
- Download Policy: Immediate
- Mirror on Sync: No (uncheck)
- Checksum: sha1 (for example, or just other type than the upstream repo has)
(other options stays default)
2. Sync the repo
3. Check the repomd.xml at <Published_At>/repodata/repomd.xml
Actual results:
It has the same checksum type as the upstream repo, not the one we selected during repo creation.
Expected results:
Same checksum type as selected.
Additional info:
Also tried on 6.9 and 6.7, there is the checksum type reflected correctly there.
Comment 1Tanya Tereshchenko
2021-09-06 20:53:30 UTC
Justin, could you check how katello sets a checksum type for a publication?
For metadata (repomd.xml), you need to set `metadata_checksum_type`, and for packages (in primary.xml and the rest), you need to set `package_checksum_type`.
I can't reproduce the issue upstream.
Verified.
Tested on: Satellite-6.10.0 Snap 21.0
Steps followed:
1. Have a Satellite, create a new Product and Repository in it with these options:
- Type: yum
- Upstream URL: https://fixtures.pulpproject.org/rpm-with-sha-512/ (for example)
- Download Policy: Immediate
- Mirror on Sync: No (uncheck)
- Checksum: sha1 (for example, or just another type than the upstream repo has)
(other options stays default)
2. Sync the repo
3. Check the repomd.xml at <Published_At>/repodata/repomd.xml
Observation: Same checksum type as selected during the repository creation.
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.10 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:4702