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:
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)
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 ***