Issue #4006
Multi-Artifact Content Units receive Duplicate Key Error with DeclarativeVersion
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
Multi-Artifact Content units work now
The artifact downloader was not instantiating the Artifacts correctly which caused duplicate key errors.
History
#1
Updated by bmbouter about 2 years ago
PR available at: https://github.com/pulp/pulp/pull/3628
#2
Updated by bmbouter about 2 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset pulp|c683ec82c4b43dc1316b7f3923641389ae4e8e60.
#3
Updated by daviddavis over 1 year ago
- Sprint/Milestone set to 3.0.0
#4
Updated by bmbouter over 1 year ago
- Tags deleted (
Pulp 3)
Please register to edit this issue
.
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