Project

Profile

Help

Story #1878

closed

Support for choosing the checksum type in updateinfo

Added by dgregor@redhat.com almost 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
2.10.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 4
Quarter:

Description

Given errata where the package list has checksums of multiple types, pulp can publish only one of those types, and filter out any others.

When pulp generates updateinfo.xml as part of a yum publish, it has logic for choosing the checksum type(s) based on the checksum(s) in the errata metadata and the checksum type of the repo. For example, if the repo is configured for sha256 and the errata metadata includes both md5 and sha256, pulp will use sha256. For backward-compatibility reasons, it is sometimes needed to use a checksum type in updateinfo that is different than the checksum type of the repo itself. Please have a way to optionally configure a checksum type for updateinfo. When it's not set it can fall back to the checksum type of the repo.


Related issues

Related to RPM Support - Issue #1618: --checksum-type is brokenCLOSED - CURRENTRELEASEmhrivnakActions
Blocked by RPM Support - Issue #2020: Cannot provide multiple checksums when uploading an erratumCLOSED - CURRENTRELEASEttereshcActions
Actions #1

Updated by dgregor@redhat.com almost 8 years ago

  • Tracker changed from Issue to Story
  • Groomed set to No
  • Sprint Candidate set to No
Actions #2

Updated by bmbouter almost 8 years ago

  • Parent issue set to #1683
Actions #3

Updated by bmbouter almost 8 years ago

  • Related to Issue #1618: --checksum-type is broken added
Actions #4

Updated by bmbouter almost 8 years ago

  • Sprint Candidate changed from No to Yes

This makes sense to me but needs to be groomed by another Pulp developer and marked as Groomed=True.

Actions #5

Updated by mhrivnak almost 8 years ago

I assume the checksums being referred to are the rpm checksums in the package list?

Dennis, are you asking for:

  • Given errata where the package list has checksums of multiple types, pulp can publish only one of those types, and filter out any others.

or are you asking for:

  • Pulp can publish an erratum using any supported checksum type. If publish is requested with a checksum type where those values are not already in the package list for any given erratum, pulp will go find the relevant RPMs in the database (assuming they are in the repo), and retrieve the checksums.

The former is easy. The latter is complex. An Errata unit in pulp does not have a direct association with RPMs, so retrieving a checksum value would require a unit search by nevra within the repo for each RPM. That could obviously add substantial time if there are many errata.

And if you want the latter, is md5 a checksum type we would need to support retrieval for? We have only been planning to store sha1 and sha256 checksums on RPM units.

Actions #6

Updated by mhrivnak almost 8 years ago

  • Sprint Candidate changed from Yes to No
Actions #7

Updated by dgregor@redhat.com almost 8 years ago

Just asking for the former: "Given errata where the package list has checksums of multiple types, pulp can publish only one of those types, and filter out any others."

Actions #8

Updated by bmbouter almost 8 years ago

  • Sprint Candidate changed from No to Yes
Actions #9

Updated by mhrivnak almost 8 years ago

  • Description updated (diff)
  • Groomed changed from No to Yes
Actions #10

Updated by mhrivnak almost 8 years ago

  • Sprint/Milestone set to 22
Actions #11

Updated by ttereshc almost 8 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
Actions #12

Updated by ttereshc almost 8 years ago

  • Blocked by Issue #2020: Cannot provide multiple checksums when uploading an erratum added

Added by ttereshc almost 8 years ago

Revision 1b7f1dc8 | View on GitHub

Add support for choosing the checksum type in updateinfo.xml

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

Actions #13

Updated by ttereshc almost 8 years ago

  • Status changed from ASSIGNED to POST
Actions #14

Updated by ttereshc almost 8 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #15

Updated by ttereshc almost 8 years ago

  • Platform Release set to 2.10.0
Actions #16

Updated by semyers over 7 years ago

  • Status changed from MODIFIED to 5
Actions #17

Updated by semyers over 7 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #18

Updated by bmbouter about 6 years ago

  • Sprint set to Sprint 4
Actions #19

Updated by bmbouter about 6 years ago

  • Sprint/Milestone deleted (22)
Actions #20

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF