Project

Profile

Help

Issue #8644

Possibly wrong checksum type in repomd.xml on publish

Added by sskracic@redhat.com 9 months ago. Updated 7 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Master
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 96
Quarter:

Description

I'm working off the 'master' branch of pulp-rpm trying to get a glimpse of repo autopublish feature - I know it has not yet been released, so I have been warned. Nevertheless, I would like to report a possible issue with checksum type in repomd.xml when autopublish feature is used. Even when both package and metadata checksum types are set to 'sha1', the checksum used in repomd.xml is sha256. Here's a sample for a RHEL 5 repo synced from cdn.redhat.com:

<repomd>
<revision>1619601758</revision>
<data type="primary">
<checksum type="sha256">
0f36c55b27e3af5c9c3c13a79e2a438baf9518a98737eeb79481d0f13fd13d2f
</checksum>
<open-checksum type="sha256">
35424b6b8f28b9890e4a69e2fa60a3dc230c5c3a1a55d440ebf95446da21649c
</open-checksum>
...

rendering it unreadable from RHEL 5 yum clients. However, the publication itself has both checksum types set to 'sha1' as expected, and 'sha1' is indeed used for package checksums in primary.xml.gz - so only the repomd.xml file itself carries the wrong checksums. I'm running Pulp 3 on RHEL8, btw (I couldn't find it in OS menu dropdown).


Related issues

Related to RPM Support - Backport #8752: Backport #8644 to 3.11CLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision f14be05d View on GitHub
Added by dalley 9 months ago

Fix wrong checksum being used for publication

closes: #8644 https://pulp.plan.io/issues/8644

History

#1 Updated by sskracic@redhat.com 9 months ago

  • Description updated (diff)

#2 Updated by dalley 9 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 95

#3 Updated by sskracic@redhat.com 9 months ago

It looks like this issue happens regardless of the autopublish flag.

#4 Updated by dalley 9 months ago

  • Status changed from NEW to POST
  • Assignee set to dalley

#6 Updated by rchan 9 months ago

  • Sprint changed from Sprint 95 to Sprint 96

#7 Updated by dalley 9 months ago

  • Status changed from POST to MODIFIED

#11 Updated by ttereshc 8 months ago

#12 Updated by ttereshc 8 months ago

  • Sprint/Milestone set to 3.12.0

#13 Updated by pulpbot 8 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#15 Updated by dalley 7 months ago

  • Subject changed from Possibly wrong checksum type in repomd.xml when autopublish is used to Possibly wrong checksum type in repomd.xml on publish

Also available in: Atom PDF