Bug 1657302

Summary: HTTP Proxies option called "HTTP Capsules" in menus.
Product: Red Hat Satellite 6 Reporter: Perry Gagne <pgagne>
Component: BrandingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: tstrych
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: ehelms, inecas, jhutar, lzap, sshtein
Target Milestone: 6.5.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: tfm-rubygem-foreman_theme_satellite- Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:39:23 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:
Description Flags
Screen shot of HTTP Capsule/Proxies page none

Description Perry Gagne 2018-12-07 16:00:18 UTC
Created attachment 1512600 [details]
Screen shot of HTTP Capsule/Proxies page

Description of problem: See attached screen shot, there seems to be a bug in the branding logic that renames the menu button for HTTP Proxies to "HTTP Capsules". 

Version-Release number of selected component (if applicable): 6.5.0 snap 5

How reproducible: Always

Steps to Reproduce:
1. Open "Infrastructure" menu

Actual results:
Option for "HTTP Capsules"

Expected results:
Should be "HTTP Proxies" 

Additional info:
This doesn't seem to be an issue in 6.4. Also not sure if its the same bug as bz 1646357 so I filed it separately.

Comment 4 Shimon Shtein 2019-02-24 14:12:21 UTC
*** Bug 1679056 has been marked as a duplicate of this bug. ***

Comment 7 tstrych 2019-03-19 12:30:43 UTC
Problem reproduced with a sat-6.5.0 snap 18 with package verion tfm-rubygem-foreman_theme_satellite-

Expected result - "HTTP Proxies" is shown, I used sat-6.5.0 snap 20. with package version tfm-rubygem-foreman_theme_satellite-


Comment 9 errata-xmlrpc 2019-05-14 12:39:23 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.