Bug 1479754 - extlogout page shows Foreman logo
extlogout page shows Foreman logo
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Branding (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: GA
: --
Assigned To: satellite6-bugs
Nikhil Kathole
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-08-09 06:51 EDT by Evgeni Golov
Modified: 2018-02-21 12:02 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-02-21 12:02:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
wrong logo on extlogout page (58.55 KB, image/png)
2017-08-09 06:51 EDT, Evgeni Golov
no flags Details
screenshot of UI (247.02 KB, image/png)
2017-09-24 04:57 EDT, Nikhil Kathole
no flags Details

  None (edit)
Description Evgeni Golov 2017-08-09 06:51:02 EDT
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 05:57:50 EDT
Moving to post, since the PR is merged to theme's master.
Comment 3 Nikhil Kathole 2017-09-24 04:56:34 EDT

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 04:57 EDT
Created attachment 1330116 [details]
screenshot of UI
Comment 5 Bryan Kearney 2018-02-21 12:02:28 EST
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.


Note You need to log in before you can comment on or make changes to this bug.