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

Bug 1252762

Summary:	[RFE][virt-v2v] When no virt-v2v exists in the Host, it could be great if an audit log will suggest that the user might need to install virt-v2v on the Host
Product:	[Retired] oVirt	Reporter:	Maor <mlipchuk>
Component:	ovirt-engine-core	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6	CC:	amureini, bugs, ecohen, gklein, lsurette, ofrenkel, rbalakri, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-13 14:43:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2015-08-12 08:35:24 UTC

Description of problem:
When no virt-v2v exists in the Host, it could be great if an audit log will suggest that the user might need to install virt-v2v on the Host.

Currently there is such log at the VDSM log, showing:
OSError: [Errno 2] No such file or directory: virt-v2v

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


How reproducible:


Steps to Reproduce:
1. Try to import a VM using virt-v2v and use a Host which does not has virt-v2v installed
2. 
3.

Actual results:
Import fails
VDSM log show: OSError: [Errno 2] No such file or directory: virt-v2v

Expected results:
Until virt-v2v will be dependent on VDSM, if a message/audit log suggesting the  user, one should install virt-v2v, it could be great.

Additional info:

Comment 1 Allon Mureinik 2015-08-12 10:15:07 UTC

This IMHO isn't an RFE, it's a bug.
VDSM can report the presence of v2v in the getCaps() verb, and the engine could grey out the the relevant button with a tooltip prompting the admin to install v2v.
(a similar solution was implemented to detect gluster support, see bug 1183318)

Comment 2 Omer Frenkel 2015-08-13 14:43:02 UTC

it was decided that vdsm will depend on v2v, so this shouldnt happen.
please see bug 1250376

*** This bug has been marked as a duplicate of bug 1250376 ***