Actions
Issue #1094
closed
repodata wrongly created for copied rpms
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.6.1
Platform Release:
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
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.
Actions
.