Actions
Issue #8625
closedRemote artifacts are not created for content which checksum type is not sha256
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 95
Quarter:
Description
This behavior was introduced with this commit. https://github.com/pulp/pulpcore/commit/47e5cc2a69464caaefbb50f994de03d72fb780e4
It affects RPM sync (because RPM content can have various checksum types) and migration plugin. Probably pulp_deb as well.
To reproduce:
- trigger on_demand sync for a repo with sha1 checksum type for content, e.g. https://packagecloud.io/timescale/timescaledb/el/7/x86_64/
- observe only one remote artifact in the db
pulp=> select url from core_remoteartifact;
url
----------------------------------------------------------------------------------------------------
https://packagecloud.io/timescale/timescaledb/el/7/x86_64/timescaledb-tools-0.8.1-0.el7.x86_64.rpm
(1 row)
If you try to fetch any content other than the one for which you have a remote artifact, you'll get 404.
Related issues
Updated by ggainey over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ggainey
Updated by pulpbot over 3 years ago
- Status changed from ASSIGNED to POST
Added by ggainey over 3 years ago
Updated by ggainey over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|eda2c890214a76e6f6ffa18cc939d04273b1fa13.
Updated by ttereshc over 3 years ago
- Related to Backport #8652: Backport #8625 to 3.12 added
Updated by ttereshc over 3 years ago
- Related to Backport #8651: Backport #8625 to pulpcore 3.7 added
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Fix artifact_stages to not uniquify based on an empty checksum-type.
fixes #8625 [nocoverage]