Bug 1350501 - v2v: '?' tooltip in import dialog is located incorrectly.
Summary: v2v: '?' tooltip in import dialog is located incorrectly.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ovirt-4.0.2
: 4.0.2
Assignee: Shahar Havivi
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-27 15:23 UTC by Nisim Simsolo
Modified: 2016-07-27 10:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-27 10:08:24 UTC
oVirt Team: Virt
Embargoed:
michal.skrivanek: ovirt-4.0.z?
mgoldboi: planning_ack+
michal.skrivanek: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)
import dialog screenshot (47.50 KB, image/png)
2016-06-27 15:25 UTC, Nisim Simsolo 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 60203 0 None None None 2016-07-05 11:12:07 UTC
oVirt gerrit 60246 0 ovirt-engine-4.0 MERGED v2v: vmware tooltip in import dialog is located incorrectly 2016-07-10 08:34:45 UTC

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
Note You need to log in before you can comment on or make changes to this bug.