Bug 1479754

Summary: extlogout page shows Foreman logo
Product: Red Hat Satellite Reporter: Evgeni Golov <egolov>
Component: BrandingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, ehelms, inecas, jcallaha, nkathole, sshtein, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 17:02:28 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
wrong logo on extlogout page
screenshot of UI none

Description Evgeni Golov 2017-08-09 10:51:02 UTC
Created attachment 1311164 [details]
wrong logo on extlogout page

Description of problem:
While verifying https://bugzilla.redhat.com/show_bug.cgi?id=1369336, I noticed that the logo on the left is wrong, it shows the FOreman hardcap, not Red Hat Satellite.

Version-Release number of selected component (if applicable):
(6.3 Snap 10)

How reproducible:

Steps to Reproduce:
1. go to https://sat6/users/extlogout

Actual results:
Foreman logo on the left

Expected results:
Satellite logo on the left

Additional info:

Comment 2 Shimon Shtein 2017-08-13 09:57:50 UTC
Moving to post, since the PR is merged to theme's master.

Comment 3 Nikhil Kathole 2017-09-24 08:56:34 UTC

Version Tested:
Satellite-6.3 Snap 17

1. Navigated to https://sat6/users/extlogout

Found Satellite logo.(see attachment)

Comment 4 Nikhil Kathole 2017-09-24 08:57:10 UTC
Created attachment 1330116 [details]
screenshot of UI

Comment 5 Bryan Kearney 2018-02-21 17:02:28 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.