Bug 970271

Summary: rpm repo publish operation claims to fail
Product: [Retired] Pulp Reporter: Michael Hrivnak <mhrivnak>
Component: rpm-supportAssignee: Jay Dobies <jason.dobies>
Status: CLOSED WORKSFORME QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Master   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-03 21:07:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
end of the publish log activity none

Description Michael Hrivnak 2013-06-03 20:53:01 UTC 
Created attachment 756514 [details]
end of the publish log activity

An rpm repo publish claims to fail. See the attached log file excerpt. Note below that the "Generating metadata" step fails. In the log file, there is one ERROR statement complaining on behalf of modifyrepo, but in the task report, there are no errors.

I've demonstrated this with a rhel6 repo and with a pulp repo. The latter is obviously much quicker to reproduce.

--------------

$ pulp-admin rpm repo publish run --repo-id=rhel6
+----------------------------------------------------------------------+
                     Publishing Repository [rhel6]
+----------------------------------------------------------------------+

This command may be exited by pressing ctrl+c without affecting the actual
operation on the server.

Publishing packages...
[==================================================] 100%
Packages: 10356/10356 items
... completed

Publishing distributions...
[==================================================] 100%
Distributions: 0/0 items
... completed

Generating metadata
[|]
... failed

Publishing repository over HTTPS
[-]
... completed
Comment 1 Michael Hrivnak 2013-06-03 21:07:13 UTC 
This was fixed by upgrading from createrepo-0.9.9-18.fc18.noarch to createrepo-0.9.9-21.fc18.noarch