Bug 1318008

Summary: Error when trying to import VM from VMware using external VMware provider.virt-v2v
Product: [oVirt] ovirt-distribution Reporter: Stig <saqp>
Component: GeneralAssignee: Arik <ahadas>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.3CC: bugs, rmcswain, tjelinek, ylavi
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-23 12:30:58 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:
Attachments:
Description Flags
Engine.log,VDSM.log,Virt-v2v-version none

Description Stig 2016-03-15 18:23:20 UTC 
Created attachment 1136685 [details]
Engine.log,VDSM.log,Virt-v2v-version

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 Tomas Jelinek 2016-03-23 12:30:58 UTC 

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