Re-uploading results in old file still being served
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-184.108.40.206.tar.bz2,c2a1985f371a8152b96c8927511e7402d2bbf64e2acb084470ec462df97b1bcc,11582712 foreman-220.127.116.11.tar.bz2,aa7bdcc0c30e2a843a1f74672292d04231749d5b8859e41b597129826ecc8f96,29676401 foreman-18.104.22.168.tar.bz2,f217c027bde37e426ccd8912b48c2f817621b7586359317cd338d5476c2f8a58,11586229 foreman-22.214.171.124.tar.bz2,2b5fc81f743de034eb38232a3d60467b3b71e819c84729a2fdcfedbfd1e3ae86,11583659 foreman-126.96.36.199.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)
Updated by email@example.com almost 6 years ago
Currently this is biting me personally when I try to rebuild a source file and upload it store on a dogfooding server. I imagine if it hits me, it will eventually hit users that begin to make more use of the generic file type repository. I can file a BZ if you like, there is not one currently.
Updated by bmbouter over 3 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.