Project

Profile

Help

Issue #8619

RPM Sync Issue - Duplicate content

Added by wibbit about 2 months ago. Updated about 2 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Q2-2021

Description

I've hit an odd sync issue with rpm (https://pulp.plan.io/issues/8615).

This is syncing against a pulp2 repo that is populated using pulp-admin's upload facility. I think I may know the cause, though this is conjecture.

Speaking with ttereshc, it's been confirmed that the upload command has the same issue as copying content between repositories does not perform any kind of de-duplication of data where the NEVRA is the same, but the hash differs.

I worked around this issue by creating a "dummy" repository, copying the content into it, and then setting the original repository up, to have it's feed set to the dummy repository and syncing it, this then engages the deduplication logic.

A subsequent sync of this repository from Pulp3 worked cleanly.

It strikes me, that Pulp3 probably should have been able to deal with this gracefully, I'm not familiar enough with sync logic to understand where the core problem was.

History

#1 Updated by fao89 about 2 months ago

  • Project changed from Pulp to RPM Support

#2 Updated by dalley about 2 months ago

  • Triaged changed from No to Yes
  • Quarter set to Q2-2021

Please register to edit this issue

Also available in: Atom PDF