Bug 970071 - Need to update OpenStack distribution logo for Login screen.
Summary: Need to update OpenStack distribution logo for Login screen.
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon   
(Show other bugs)
Version: 3.0
Hardware: Unspecified Linux
Target Milestone: snapshot2
: 3.0
Assignee: Matthias Runge
QA Contact: Nir Magnezi
Keywords: Regression
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-03 12:21 UTC by Nir Magnezi
Modified: 2016-04-26 16:22 UTC (History)
6 users (show)

Fixed In Version: python-django-horizon-2013.1.1-4.el6ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-11 18:40:09 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0932 normal SHIPPED_LIVE python-django-horizon bug fix update 2013-06-11 22:38:01 UTC

Description Nir Magnezi 2013-06-03 12:21:47 UTC
Description of problem:
The Redhat Logo is missing from the logic screen.
The Logo should be the same as the logo at the upper left side corner (after user logged in)

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

How reproducible:

Steps to Reproduce:
1. Browse to: http://<host>/dashboard/auth/login/

Actual results:
Openstack Logo without Redhat Logo

Expected results:
As described in problem description.

Comment 3 Matthias Runge 2013-06-03 14:37:59 UTC
There was a second logo introduced (a larger and a smaller one) The one for the login page should be the larger one.

Comment 5 Nir Magnezi 2013-06-05 11:33:20 UTC
Verified NVR: python-django-horizon-2013.1.1-4.el6ost.noarch

The logo looks OK now.

Comment 7 errata-xmlrpc 2013-06-11 18:40:09 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.


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