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.
DescriptionJustin Sherrill
2016-03-29 19:35:46 UTC
Description of problem:
When creating a puppet repo within sat6 we do not actually publish the empty repo. The result of that is that when the capsule syncs, that puppet repo will fail to sync and throw an error
Version-Release number of selected component (if applicable):
Sat 6.2 snap 4
How reproducible:
Always
Steps to Reproduce:
1. Create a puppet repo, do not upload or sync any modules
2. Sync a capsule that is attached to the library environment
Actual results:
Capsule sync Task will error and be left in 'warning state'
Expected results:
Capsule sync task is successful
Additional info:
For yum repos we 'publish' the metadata for them at creation time. We should do the same for puppet repos
Moving to POST since upstream bug http://projects.theforeman.org/issues/14512 has been closed
-------------
John Mitsch
Applied in changeset commit:katello|0a7fa53d0cb5a78b5046538f85656ccafd14f22f.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501