Project

Profile

Help

Issue #2433

closed

Re-uploading results in old file still being served

Added by ehelms@redhat.com over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.8.7
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Using the iso type of repository, a user can upload the same file multiple times. However, the 'last' one to be uploaded is the not the current one being served by the repository. The generated PULP_MANIFEST indicates the various versions of this file that have been uploaded but they appear in semi-random order. An example:

foreman-1.13.1.1.tar.bz2,c2a1985f371a8152b96c8927511e7402d2bbf64e2acb084470ec462df97b1bcc,11582712
foreman-1.13.1.1.tar.bz2,aa7bdcc0c30e2a843a1f74672292d04231749d5b8859e41b597129826ecc8f96,29676401
foreman-1.13.1.1.tar.bz2,f217c027bde37e426ccd8912b48c2f817621b7586359317cd338d5476c2f8a58,11586229
foreman-1.13.1.1.tar.bz2,2b5fc81f743de034eb38232a3d60467b3b71e819c84729a2fdcfedbfd1e3ae86,11583659
foreman-1.13.1.1.tar.bz2,4cde275645bafe5b46448925dec1c6b295119bcd4b4b4ab76cc04f38109f2398,29859413
foreman_theme_satellite-1.0.0.gem,03f8ac79b51cb68f9308249396881a827d5b81840bed58bf466133cef6c37120,158720

Further, this behavior appears with the YUM repository type as well. A user can:

1) sync a repository
2) upload an RPM that was synced down with a different checksum (maybe the underlying source changed)
3) Pulp will accept the upload with success
4) check the yum metadata and note both checksums in it but only one copy of the RPM in the repo (this will lead to yum errors)

Also available in: Atom PDF