Hide Forgot
We lost the Capsule branding we have in 6.1 1) New/Edit Hosts Form: CAPSULE SETTINGS - Content Source - Puppet CA - Puppet Master 2) New/Edit Host Group Form: CAPSULE SETTINGS - Content Source - Puppet CA - Puppet Master 3) Infrastructure -> Capsules - New Capsule button Screenshots from 6.1 will be attached.
Created attachment 1139719 [details] new host screenshot
IMHO the only thing that is missing is the "capsule settings" title, but I can't see it in katello upstream override either. (https://github.com/Katello/katello/blob/master/app/views/overrides/activation_keys/_host_environment_select.html.erb) The title was problematic anyway, because other plugins can add fields to host too. We already have such field in the latest build: OpenSCAP proxy, which is located under the original katello override, so the title would be a bit misleading. About Capsule <-> Smart proxy - it is what Satellite theme process should handle. It should be done via en.po file.
We don't do the Capsule Settings title in upstream, this is Satellite only. That said, with the addition of the new fields on this form, adding that title now seems a bit confusing so I think some discussion on how to call out the capsule settings is in order. Will also ensure we re-run the downstream branding process to get the Smart Proxy>Capsule rename in the menus.
1),2) The "Capsule Settings" titles are no longer present in New Host|Hostgroup forms for Snap 7. Was this intended? 3) Infrastructure -> Capsules - New Capsule button = VERIFIED
Created attachment 1145109 [details] snap7- new_host
Not exactly my decision to make, but according to Mike [1] it should be gone. Mike? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1320701#c4
I filed a separate BZ specifically for just the Capsule Settings on new host/hostgroup page: https://bugzilla.redhat.com/show_bug.cgi?id=1328523 so, if the other issues are OK, I'd mark this VERIFIED
Marking this VERIFIED according to Comment #11
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