Bug 1203853

Summary: [branding] New host form missing branding
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: WebUIAssignee: Shimon Shtein <sshtein>
WebUI sub component: Katello QA Contact: Sachin Ghai <sghai>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: bkearney, cwelton, jmontleo, ohadlevy, sthirugn
Version: 6.1.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:30:24 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:
Attachments:
Description Flags
Satellite 6.0 New Host Form
none
Sat 6.1 new host form none

Description Mike McCune 2015-03-19 18:53:13 UTC
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

Comment 6 Sachin Ghai 2015-04-02 13:07:59 UTC
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

Comment 7 Sachin Ghai 2015-04-02 13:09:42 UTC
Created attachment 1010158 [details]
Sat 6.1 new host form

Comment 8 Bryan Kearney 2015-08-11 13:37:18 UTC
This bug is slated to be released with Satellite 6.1.

Comment 9 errata-xmlrpc 2015-08-12 05:30:24 UTC
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