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.

Created attachment 1004132 [details]
Satellite 6.0 New Host Form

In Satellite 6.0 we had a sub-form called out for Content Settings that called out some specific fields for determining where the Host pulls content from. 

See attached screenshot of how it looks in *6.0*.

This sub-section of the New Host form was lost in the re-branding of Satellite 6.1 and needs to be restored.  Currently these fields are not showing in the sub-area.

If you view New Host in 6.1 it is just a big form with no sub-area

Verified in sat6.1 beta snap9(Satellite-6.1.0-RHEL-6-20150331.1).

I can see the same branding (separate capsule settings section) in sat6.1 UI. please see the screenshot. Thanks

Created attachment 1010158 [details]
Sat 6.1 new host form

This bug is slated to be released with Satellite 6.1.

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/RHSA-2015:1592