Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1033777

Summary: Never synced custom repositories fail to publish
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.2CC: cwelton, jmontleo
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1033776 Environment:
Last Closed: 2014-04-24 17:09:05 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:
Bug Depends On: 1033776    
Bug Blocks:    

Description Justin Sherrill 2013-11-22 20:59:53 UTC
+++ 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.

Comment 3 Corey Welton 2013-12-04 02:32:57 UTC
QA Verified in Satellite-6.0.2-RHEL-6-20131202.0

Comment 6 Bryan Kearney 2014-04-24 17:09:05 UTC
This was verified and delivered with MDP2. Closing it out.

Comment 7 Bryan Kearney 2014-04-24 17:10:40 UTC
This was delivered and verified with MDP2. Closing the bug.