Bug 970271 - rpm repo publish operation claims to fail
rpm repo publish operation claims to fail
Product: Pulp
Classification: Community
Component: rpm-support (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jay Dobies
Preethi Thomas
Depends On:
  Show dependency treegraph
Reported: 2013-06-03 16:53 EDT by Michael Hrivnak
Modified: 2013-06-03 17:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-03 17:07:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
end of the publish log activity (1.98 KB, text/x-log)
2013-06-03 16:53 EDT, Michael Hrivnak
no flags Details

  None (edit)
Description Michael Hrivnak 2013-06-03 16:53:01 EDT
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 17:07:13 EDT
This was fixed by upgrading from createrepo-0.9.9-18.fc18.noarch to createrepo-0.9.9-21.fc18.noarch

Note You need to log in before you can comment on or make changes to this bug.