Bug 1318008 - Error when trying to import VM from VMware using external VMware provider.virt-v2v
Summary: Error when trying to import VM from VMware using external VMware provider.vir...
Keywords:
Status: CLOSED DUPLICATE of bug 1318011
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: General
Version: 3.6.3
Hardware: x86_64
OS: Linux
unspecified
low vote
Target Milestone: ---
: ---
Assignee: Arik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 18:23 UTC by Stig
Modified: 2020-12-02 21:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 12:30:58 UTC
oVirt Team: Virt
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Engine.log,VDSM.log,Virt-v2v-version (916.27 KB, application/zip)
2016-03-15 18:23 UTC, Stig 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.