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

Bug 1354511

Summary: v2v: import dialog - tooltip for URI field of XEN source is truncated
Product: [oVirt] ovirt-engine Reporter: Sharon Gratch <sgratch>
Component: BLL.VirtAssignee: Sharon Gratch <sgratch>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.0.1CC: bugs, mgoldboi, sbonazzo, tgolembi, tjelinek
Target Milestone: ovirt-4.0.4Flags: rule-engine: ovirt-4.0.z+
mgoldboi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 4.0.4   
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-09-26 12:40:12 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
screenshot
none
vdsm log none

Description Sharon Gratch 2016-07-11 12:58:23 UTC
Created attachment 1178393 [details]
screenshot

Description of problem:
In import vms dialog (v2v) for XEN external source, the tooltip for the URI field is displayed as follows:
"Replace '<hostname>' with the hostname of the Xen hypervisor in the libvirt URI.
Only SSH transport is allowed for Xen import and the connection has to be without password. 

To disable SSH host key verification add 'no_verify' parameter to the 
URI, i.e.: 
xen+ssh://root.com?no"


Two issues with this tooltip:
1. It is triuncated. The full last line should be:
xen+ssh://root.com?no_verify=1</i>"
2. The no_verify flag doesn't work as described in this tooltip. the SSH key verification is not disabled when adding no_verify=1 flag.


Version-Release number of selected component (if applicable):
4.0.1

How reproducible:
100%

Steps to Reproduce:
1.open the import vms dialog and choose the XEN as Source.
2.open the tooltip of the URI field.


Actual results:
the tooltip is both truncated and not accurate in terms of the no_verify flag.

Expected results:
tooltip should be accurate.

Additional info:
see screenshot

Comment 1 Tomáš Golembiovský 2016-07-12 14:02:58 UTC
(In reply to Sharon Gratch from comment #0)

> 2. The no_verify flag doesn't work as described in this tooltip. the SSH key
> verification is not disabled when adding no_verify=1 flag.

Could you please describe how did you observe the fact that the host key verification is not disabled? Or can you attach the relevant part of VDSM log?

Comment 2 Sharon Gratch 2016-07-13 08:59:49 UTC
Created attachment 1179152 [details]
vdsm log

Comment 3 Sharon Gratch 2016-07-13 09:01:35 UTC
regarding 2) The no_verify flag doesn't work as described in this tooltip.:
I tried to connect to a proxy host which I didn't exchange the VDSM ssh keys with XEN server before doing that ->  and it failed to connect while using the no_verify=1 flag. 

VDSM error:
error connection to hypervisor: 'Cannot recv data: Permission denied, please try again
.\r\nPermission denied, please try again.\r\nPermission denied (publickey,gssapi-with-mic,password).: Connection reset by peer'

VDSM version 4.18.

Attached is the vdsm log of another proxy host for reproducing it. 
The 1st error in attached log is while trying to connect without the no_verify flag and the second ERROR is while trying to connect with the flag. Same error for both.

Comment 4 Tomáš Golembiovský 2016-07-13 12:18:24 UTC
The option is not meant to bypass user authentication. It only disables the
check whether the machine VDSM is talking to is the expected one.

If the option didn't work you would see in the VDSM log something like this:

    error connection to hypervisor: 'Cannot recv data: Host key verification failed.: Connection reset by peer'

The truncated tooltip is a problem though.

Comment 5 Red Hat Bugzilla Rules Engine 2016-07-18 14:37:02 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 meital avital 2016-09-06 13:50:26 UTC
Verified on version: rhevm-4.0.4-0.1.el7ev.noarch