Project

Profile

Help

Issue #4529

closed

Broken repo can be published if zchunk metadata is not ignored at sync time

Added by ttereshc about 5 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.19.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 52
Quarter:

Description

In Fedora 30, Zchunk metadata is going to be present alongside with older compression formats.

Pulp should ignore and not sync this metadata, in order to avoid creating a potentially bad repo at publish time.
Scenario for a bad repo:
- create repo and sync from a remote repo with zchunk metadata
- make any content changes to a repo , e.g. remove/add packages
- published a repo
- zchunk metadata is published as-is without any modifications to it (even though content in a repo changed) -> clients which use zchunk metadata will get incorrect data about the content in a repo.

Repo with this new metadata type: http://mirror.vutbr.cz/fedora/development/rawhide/Everything/x86_64/os/


Related issues

Related to RPM Support - Test #4530: Test support of zchunk metadataCLOSED - COMPLETEbherringActions

Also available in: Atom PDF