Bug 1139699 - [Admin Portal] New Cluster - Fencing Policy - ui alignment is odd
Summary: [Admin Portal] New Cluster - Fencing Policy - ui alignment is odd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.5.0
Assignee: Martin Perina
QA Contact: Petr Kubica
URL:
Whiteboard: infra
Depends On:
Blocks: rhev3.5beta3
TreeView+ depends on / blocked
 
Reported: 2014-09-09 13:22 UTC by Jiri Belka
Modified: 2016-02-10 19:20 UTC (History)
8 users (show)

Fixed In Version: org.ovirt.engine-root-3.5.0-13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:12:41 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (18.95 KB, application/octet-stream)
2014-09-09 13:22 UTC, Jiri Belka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 32939 0 master MERGED webadmin: Fix fencing policy fields alignment Never
oVirt gerrit 32988 0 ovirt-engine-3.5 MERGED webadmin: Fix fencing policy fields alignment Never

Description Jiri Belka 2014-09-09 13:22:11 UTC 
Created attachment 935695 [details]
screenshot

Description of problem:
New Cluster - Fencing Policy - ui alignment is odd, see screenshot.

Version-Release number of selected component (if applicable):
rhevm-webadmin-portal-3.5.0-0.10.master.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. see dialog
2.
3.

Actual results:
mis-alignment

Expected results:
niceeeee

Additional info:
Comment 1 Eyal Edri 2014-09-28 11:29:22 UTC 
this bug was moved to MODIFIED before vt4 build date thus moving to ON_QA.
if you belive this bug isn't in vt4, please report to rhev-integ
Comment 2 Petr Kubica 2014-10-01 11:53:26 UTC 
Verified in 3.5.0-0.13.beta.el6ev
Comment 3 Eyal Edri 2015-02-17 17:12:41 UTC 
rhev 3.5.0 was released. closing.
Note You need to log in before you can comment on or make changes to this bug.