Bug 2001052

Summary:	Selected yum metadata checksum type on is not reflected in repomd.xml on a repo creation
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Repositories	Assignee:	Ian Ballou <iballou>
Status:	CLOSED ERRATA	QA Contact:	addubey
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	addubey, iballou, jsherril, ttereshc, zhunting
Target Milestone:	6.10.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.1.1.23-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:13:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimí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 1 Tanya 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.

Comment 2 Justin Sherrill 2021-09-07 14:54:01 UTC

hrmm yeah, this seems like a katello bug

Comment 3 Ian Ballou 2021-09-15 19:09:25 UTC

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

Comment 8 addubey 2021-10-07 11:02:58 UTC

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.

Comment 11 errata-xmlrpc 2021-11-16 14:13:42 UTC

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