Bug 1384244

Summary:	Large Blank Space Present to the Left of the Content Pane in Horizon UI
Product:	Red Hat OpenStack	Reporter:	Dustin Schoenbrun <dschoenb>
Component:	python-django-horizon	Assignee:	Radomir Dopieralski <rdopiera>
Status:	CLOSED DUPLICATE	QA Contact:	Ido Ovadia <iovadia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	aortega, athomas, mrunge, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-20 17:56:14 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 Dustin Schoenbrun 2016-10-12 22:41:56 UTC

Description of problem:
When you log into the Horizon UI that has been installed via OSP-Director and navigate to any page in the UI there is a large blank space on the left side of the screen. 

Version-Release number of selected component (if applicable):
python-django-horizon-10.0.0-0.20161002185148.3252153.1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install an OpenStack instance with OSP-Director.
2. Navigate to the Horizon UI for the Overcloud and log in.
3. Observe that there is a large pad of blank space on the left side of the main content pane.

Actual results:
There is a large pad of blank space on the left side of the main content pane.

Expected results:
The main content pane should be aligned with the left edge of the browser.

Additional info:
I will note that this is done with the Manila Horizon UI Plugin installed. This was observed with the following versions of Google Chrome and Firefox.

Chrome  - 53.0.2785.143 (64-bit)
Firefox - 49.0

I've also attached a screenshot showing this issue appearing in Firefox.

Comment 1 Dustin Schoenbrun 2016-10-20 17:56:14 UTC


*** This bug has been marked as a duplicate of bug 1384243 ***