Bug 1291055 - v2v: Conversion of VM from VMware environment failed with "HTTP/1.1 404 Not Found".
v2v: Conversion of VM from VMware environment failed with "HTTP/1.1 404 Not F...
Status: CLOSED DUPLICATE of bug 1292096
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs (Show other bugs)
Unspecified Unspecified
unspecified Severity urgent
: rc
: ---
Assigned To: Richard W.M. Jones
Virtualization Bugs
Depends On:
Blocks: 952703 1236075
  Show dependency treegraph
Reported: 2015-12-13 04:09 EST by Nisim Simsolo
Modified: 2016-02-17 09:40 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
VMware vCenter server 6.0.0 build 2656760 VMware ESXi server 6.0.0 build 2494585 RHEVM engine - RHEVM hosts - RHEL 7.2
Last Closed: 2016-01-07 09:19:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
vdsm.log (936.15 KB, application/x-gzip)
2015-12-13 04:10 EST, Nisim Simsolo
no flags Details
engine.log (512.28 KB, application/x-gzip)
2015-12-13 04:10 EST, Nisim Simsolo
no flags Details

  None (edit)
Description Nisim Simsolo 2015-12-13 04:09:22 EST
Description of problem:
Trying to import VMware VM from RHEVM failed with "HTTP/1.1 404 Not Found" when trying to get storage path.
VMware environment is 6.0.0 licensed and VMware VM I'm trying to import is with NFS disk.

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

How reproducible:

Steps to Reproduce:
1. From vSphere client, create DC -> Cluster -> add host -> create VM with NFS storage (keep VM powered off during the next steps).
2. Open RHEVM, navigate to virtual machines tab -> click import.
3. Enter vCenter details and credentials -> click "load"
4. Select one of the VMs that were listed to import and click "next".
5. Select host and storage domain destination -> click "ok"

Actual results:
After import process started, it failed during import VM disk phase with the next engine.log (IP address changed to 10.X.X.X by me):
2015-12-13 10:15:40,742 INFO  [org.ovirt.engine.core.bll.ConvertVmCallback] (DefaultQuartzScheduler_Worker-27) [] Conversion of VM from exteral enironment failed: Job u'423c3d8c-15e9-4650-f0fa-02d0a8332ea9' process failed exit-code: 1, stderr: curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.X.X.X/folder/rhel7/rhel7-flat.vmdk?dcPath=Compute/cluster&dsName=storage'
HTTP/1.1 404 Not Found
Date: Sun, 13 Dec 2015 08:16:14 GMT
Set-Cookie: vmware_soap_session="c905314a0fd3cec35f9442c995f067b3704e08ec"; Path=/; HttpOnly; Secure; 
Connection: close
Content-Type: text; charset=plain
Content-Length: 0

virt-v2v: error: vcenter: URL not found:

Expected results:
Import VM should succeed.

Additional info:
engine.log and vdsm.log attached.
vdsm issue occurred at: Thread-29651::ERROR::2015-12-13 10:16:14,715
engine issue occurred at: 2015-12-13 10:15:40,742
Comment 1 Nisim Simsolo 2015-12-13 04:10 EST
Created attachment 1105283 [details]
Comment 2 Nisim Simsolo 2015-12-13 04:10 EST
Created attachment 1105284 [details]
Comment 3 Nisim Simsolo 2015-12-13 06:33:29 EST
I also tried to disable SELinux and turn off iptables, issue is still reproduced.
Comment 4 Richard W.M. Jones 2015-12-13 10:13:23 EST
This is probably a duplicate of

There are only two realistic solutions to this:

(1) Modify the UI so that the user can pass in the dcpath
parameter (which is then passed through to the virt-v2v
command line).

However that's going to be annoying to document, so a
better solution is:

(2) Wait for RHEL 7.3 where a combination of libguestfs and
libvirt [bug 1263574] updates will fix this automatically
without any need to use --dcpath.

In any case, we cannot solve this in libguestfs.
Comment 5 Richard W.M. Jones 2015-12-13 10:16:28 EST
BTW neither of the log files contains any useful information.  To
really diagnose if this is a duplicate, I need the output of the
'virt-v2v -v -x' command.
Comment 6 Michal Skrivanek 2016-01-07 09:12:28 EST
based on comment #4, and assuming bug 1263574 and bug 1292437 get the backport approval, there is indeed no need to track this separately

Richard, if you're fine with that I would close as dupe of RHEV bug 1292096
Comment 7 Richard W.M. Jones 2016-01-07 09:19:37 EST
Closing as duplicate per comment 6.

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

Note You need to log in before you can comment on or make changes to this bug.