+++ This bug was initially created as a clone of Bug #1033776 +++ Description of problem: Custom repositories do not seem to publish properly, and thus the content is not available to clients. Version-Release number of selected component (if applicable): pulp-server-2.3.0-0.37.beta.el6sat.noarch How reproducible: Always Steps to Reproduce: 1. Create a new custom repo 2. Upload a package to it from the cli 3. Assign a system to the custom product and try to install the pushed rpm Actual results: From client repository shows that it contains no packages, system cannot install package. Expected results: Client sees package, can install it. Additional info: Error seen in /var/log/pulp/pulp.log: 2013-11-22 15:37:39,303 pulp.plugins.pulp_rpm.yum_plugin.metadata:ERROR: Error performing final move, could be missing pkg metadata files This is actually masking another error, and after some debugging: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pulp_rpm/yum_plugin/metadata.py", line 851, in final_repodata_move mdgen.doRepoMetadata() File "/usr/lib/python2.6/site-packages/createrepo/__init__.py", line 955, in doRepoMetadata data = misc.Checksums([sumtype]) File "/usr/lib/python2.6/site-packages/yum/misc.py", line 245, in __init__ raise MiscError, 'Error Checksumming, bad checksum type %s' % sumtype MiscError: Error Checksumming, bad checksum type None --- Additional comment from Justin Sherrill on 2013-11-22 15:59:06 EST --- I did confirm that if the repo is ever synced with an external repo the issue does not occur.
QA Verified in Satellite-6.0.2-RHEL-6-20131202.0
This was verified and delivered with MDP2. Closing it out.
This was delivered and verified with MDP2. Closing the bug.