Bug 1318011

Summary: Error when trying to import VM from VMware using external VMware provider.virt-v2v
Product: [oVirt] ovirt-distribution Reporter: Stig <saqp>
Component: GeneralAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: low Docs Contact:
Priority: medium    
Version: 3.6.3CC: bugs, mavital, mgoldboi, michal.skrivanek, nsimsolo, saqp, sbonazzo
Target Milestone: ovirt-3.6.5Flags: rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
michal.skrivanek: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-21 14:40:50 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:

Description Stig 2016-03-15 18:24:14 UTC 
Description of problem:
When I attempt to migrate VM's from the VMware platform to the Ovirt platform all goes well up until the point where the migration actually needs to start copying data from the VMware host.

VDSM log shows.
V2VProcessError: Job u'420fd066-5fdd-8a3f-1a03-9f168e73124b' process failed exit-code: 1, stderr: curl -q --insecure --user '<hidden>' --head --silent --url 'https://172.16.1.251/folder/migrateme/migrateme-flat.vmdk?dcPath=APSYS/Home&dsName=ISCSI-LUN0' 
HTTP/1.1 404 Not Found 

Version-Release number of selected component (if applicable):
engine 
virt-v2v-1.28.1-1.55.el7.centos.x86_64

Compute Node: selected proxy
virt-v2v-1.28.1-1.55.el7.centos.x86_64

How reproducible:
Consistent.


Steps to Reproduce:
1. Walkthrough as shown in Arik's instruction. 
   https://www.youtube.com/watch?v=7vd8X6t9eBk
2.
3.

Actual results:
System throws error and cleans up the VM created during the initial phase of the migration.

Expected results:
Successful migration ov VM.


Additional info:
Comment 1 Michal Skrivanek 2016-03-16 09:06:44 UTC 
is it possible you have a Cluster on VMware side? See bug 1292096 - there are fixed packages available(not yet released), maybe you can try out those? (both libvirt and v2v)
Comment 2 Stig 2016-03-16 10:40:49 UTC 
Yes the VM is in a cluster. (that’s pretty much standard for production setups) I'd love to try out the updated packages. What version do i need and do you have any pointers to where i get them?
+ if I need to do something additional.
I got the test rig running and I/we can thrash it as much as I'd like.
Comment 3 Tomas Jelinek 2016-03-23 12:30:58 UTC 
*** Bug 1318008 has been marked as a duplicate of this bug. ***
Comment 4 Michal Skrivanek 2016-03-24 14:23:18 UTC 
the fix is on v2v and libvirt side, pending updates in RHEL and CentOS, should happen in 3.6.5 timeframe
see also bug 1292096
Comment 5 Nisim Simsolo 2016-04-13 10:21:53 UTC 
Verified using VMware 6 build 2594327 and VMware 5.5 build 2893190:
rhevm-3.6.5.3-0.1.el6
qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64
vdsm-4.17.26-0.el7ev.noarch
libvirt-daemon-1.2.17-13.el7_2.4.x86_64
sanlock-3.2.4-2.el7_2.x86_64