repodata wrongly created for copied rpms
Since upgrading from 2.6beta (March 2015) to 2.6.2 stable I am getting wrong repomd.xml files generated.
This happens when I use:
pulp-admin rpm repo content rpm copy
The generated repomd.xml is sometimes pointing to tarballs that don't exist, so my yum clients are fetching updateinfo.tar.gz with a 404.
I have also reinstalled the system fresh and did another install not migrating any data, but instead reuploading all old artifacts.
A workaround that I am currently applying is downloading the rpm from one repo and using pulp-admin to upload it to the other one, which seems to never fail generating repodata properly.
#1 Updated by zottel over 6 years ago
- Status changed from NEW to CLOSED - NOTABUG
After a second repository, where we didn't use copy, failed as well, we did some more testing.
Two days of debugging later and we found out it's a cache in our company network that keeps outdated repodata for this specific server.
Sorry for the inconvenience :)
Please register to edit this issue