Bug 1350501

Summary: v2v: '?' tooltip in import dialog is located incorrectly.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: Frontend.WebAdminAssignee: Shahar Havivi <shavivi>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: low Docs Contact:
Priority: medium    
Version: 4.0.0CC: bugs, gklein, mgoldboi, michal.skrivanek, nsimsolo, tnisan
Target Milestone: ovirt-4.0.2Flags: michal.skrivanek: ovirt-4.0.z?
mgoldboi: planning_ack+
michal.skrivanek: devel_ack+
rule-engine: testing_ack?
Target Release: 4.0.2   
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-07-27 10:08:24 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
import dialog screenshot none

Description Nisim Simsolo 2016-06-27 15:23:47 UTC 
Description of problem:
When opening virtual machines import dialog, and selecting VMware, a '?' tooltip for explaining the import hierarchy path is located next to vCenter instead of Data Center.

Version-Release number of selected component (if applicable):
rhevm-4.0.0.6-0.1.el7ev
vdsm-4.18.4-2.el7ev.x86_64
libvirt-client-1.2.17-13.el7_2.5.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Browse webadmin -> Virtual machines tab -> import dialog button
2. 
3.

Actual results:
'?' tooltip is located next to vCnter instead of Data Center.

Expected results:


Additional info:
Screenshot attached
Comment 1 Nisim Simsolo 2016-06-27 15:25:23 UTC 
Created attachment 1172914 [details]
import dialog screenshot
Comment 2 Gil Klein 2016-07-27 10:08:24 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA