Project

Profile

Help

Issue #4006

Multi-Artifact Content Units receive Duplicate Key Error with DeclarativeVersion

Added by bmbouter over 1 year ago. Updated 3 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
3. High
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Problem

The pulp_gem plugin code here [0] is written correctly, and the fixture data they use is also correct [1].

I've been able to reproduce the issue described to me on IRC.

Root Cause

There is a bug in the ArtifactDownloader stage whereby a unit with multiple Artifacts incorrectly reuses the first downloader's information (incorrectly) for subsequent Artifacts. This causes the Artifact to have the same sha256 value which raises the duplicate key exception.

Solution

Fix the bug by removing the extra, incorrect loop that is present.

[0]: https://github.com/ATIX-AG/pulp_gem/blob/update_api/pulp_gem/app/tasks/synchronizing.py#L69-L95
[1]: https://repos.fedorapeople.org/pulp/pulp/demo_repos/gems/repo/

Associated revisions

Revision c683ec82 View on GitHub
Added by bmbouter over 1 year ago

Multi-Artifact Content units work now

The artifact downloader was not instantiating the Artifacts correctly which caused duplicate key errors.

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

Revision c683ec82 View on GitHub
Added by bmbouter over 1 year ago

Multi-Artifact Content units work now

The artifact downloader was not instantiating the Artifacts correctly which caused duplicate key errors.

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

History

#2 Updated by bmbouter over 1 year ago

  • Status changed from ASSIGNED to MODIFIED

#3 Updated by daviddavis 10 months ago

  • Sprint/Milestone set to 3.0.0

#4 Updated by bmbouter 10 months ago

  • Tags deleted (Pulp 3)

#5 Updated by bmbouter 3 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF