Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1115016

Summary: New Virtual Machine: uneven space between left side pane, gray and white area of the window
Product: [Retired] oVirt Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engine-webadminAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.5CC: ecohen, gklein, iheim, mgoldboi, mpavlik, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-29 09:08:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot1 none

Description Martin Pavlik 2014-07-01 12:38:33 UTC 
Description of problem:
uneven space between left side pane, gray and white area of the window (see screenshot)

Version-Release number of selected component (if applicable):
 oVirt Engine Version: 3.5.0-0.0.master.20140629172257.git0b16ed7.el6 

How reproducible:
100%

Steps to Reproduce:
1. Virtual Machines -> New

Actual results:
uneven space between left side pane, gray and white area of the window (see screenshot)

Expected results:
shrink the white area to the right so there is same distance from left side pane

Additional info:
Comment 1 Einav Cohen 2014-07-22 17:55:31 UTC 
Martin: screen-shot?
Comment 2 Martin Pavlik 2014-07-23 06:47:51 UTC 
Created attachment 920107 [details]
screenshot1
Comment 3 Michal Skrivanek 2014-08-22 14:26:16 UTC 
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
Comment 4 Itamar Heim 2015-03-29 09:08:03 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.