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.

Ensure that clients only need communication routes between themselves and the Capsule and not the main Satellite 6 server.

This is being tracked upstream at:

http://projects.theforeman.org/issues/8172

This will include the ability to deploy the

This will include the ability to deploy the certs RPM from the capsule directly to the clients.

Per triage discussion, this is a tracking bug for a feature that has been delivered. I am moving this to modieifed, and ON_QA.

Considering this tracker bug verified/closed for 6.1

This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.