Bug 1373259

Created attachment 1197983 [details]
ospita web folder screenshot

Description of problem:
Hello all,
I'm facing this issue. I'm trying to manually migrate a guest from ESX 5.5 to Ovirt 4.0.3 with the virt-v2v utility.

I tried first to connect to ESX via virsh, both vpx and esx successfully.
ESX side, the guest path is:
10.1.1.246 = Vcenter Server
AdsPmVmw = DataCenter Name
AdsCluster = Cluster Name
adspmvmware07.assembly.local = ESX 5.5 physical node

I ran the following command:
# virsh -c vpx://10.1.1.246/AdsPmVmw/AdsCluster/adspmvmware07.assembly.local?no_verify=1 

Enter username for 10.1.1.246 [xxx]: xxx
Enter xxx's password for 10.1.1.246:
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # list
 Id    Name                           State
----------------------------------------------------
 29205 AdsPmADSGroupWebsite           running
 31760 AdsPmFortiAnalyzer             running
 32412 antsDB_GRA                     running
 33647 AdsPmGroupAdsWebSite           running
 34915 Debian_8.x.D 172.161.16.141    running
 34918 Ospita_7.x                     running
 34928 OpenSuse                       running
 34930 vm04                           running
(...)


As you can see the vpx connection and the path worked correctly.

I tried the connection to the esx:

# virsh -c esx://10.1.1.249?no_verify=1
Enter username for 10.1.1.249 [root]:
Enter root's password for 10.1.1.249:
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # list --all
 Id    Name                           State
----------------------------------------------------
 8     Ospita_7.x                     running
 13    AdsPmUbuntuSviluppo            running
 16    vm04                           running
 27    Centos7_SAC                    running
 33    AdsPmADSGroupWebsite           running
 34    AdsPmGalata                    running
 38    AdsPmAsteriskPBX               running
(...)


As you can see this worked fine too.
Running the virt-v2v I tried to migrate the vm called "Ospita" and I obtained:

# virt-v2v -v -x -ic vpx://xxx.1.246/AdsPmVmw/AdsCluster/adspmvmware07.assembly.local/?no_verify=1 -o rhev -os rhgs1-stg.assembly.local:/volume-export --network ovirtmgmt Ospita

virt-v2v: libguestfs 1.28.1 (x86_64)
[   0.0] Opening the source -i libvirt -ic vpx://xxx.1.246/AdsPmVmw/AdsCluster/adspmvmware07.assembly.local/?no_verify=1 Ospita
input_libvirt_vcenter_https: source: scheme vpx server 10.1.1.246
Enter asabbatini's password for 10.1.1.246:
Enter host password for user 'xxx':
libvirt xml is:
<domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'>
  <name>Ospita</name>
  <uuid>4219806c-40bd-801d-4a1b-9f384f161178</uuid>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64'>hvm</type>
  </os>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <disk type='file' device='disk'>
      <source file='[v37kRm_10K_VMFS02] Ospita/Ospita-000001.vmdk'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <source file='[v37kRm_10K_VMFS02] Ospita/Ospita_1.vmdk'/>
      <target dev='sdc' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <source file='[v37kRm_10K_VMFS02] ISO/rhel-server-7.1-x86_64-dvd.iso'/>
      <target dev='hdc' bus='ide'/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='vmpvscsi'/>
    <controller type='ide' index='0'/>
    <interface type='bridge'>
      <mac address='00:50:56:99:51:81'/>
      <source bridge='DMZ'/>
      <model type='vmxnet3'/>
    </interface>
    <interface type='bridge'>
      <mac address='00:50:56:99:73:27'/>
      <source bridge='ProjectSelinux'/>
      <model type='vmxnet3'/>
    </interface>
    <interface type='bridge'>
      <mac address='00:50:56:99:1c:20'/>
      <source bridge='DMZ'/>
      <model type='vmxnet3'/>
    </interface>
    <video>
      <model type='vmvga' vram='8192'/>
    </video>
  </devices>
  <vmware:datacenterpath>AdsPmVmw</vmware:datacenterpath>
</domain>

vcenter: using <vmware:datacenterpath> from libvirt: AdsPmVmw
curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.1.1.246/folder/Ospita/Ospita-000001-flat.vmdk?dcPath=AdsPmVmw&dsName=v37kRm%5f10K%5fVMFS02'
HTTP/1.1 404 Not Found
Date: Mon, 5 Sep 2016 15:14:21 GMT
Set-Cookie: vmware_soap_session="52da2e5f-86e9-b035-bf39-8ca05761e6db"; Path=/; HttpOnly; Secure;
Connection: close
Content-Type: text; charset=plain
X-Frame-Options: DENY
Content-Length: 0

curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.1.1.246/folder/Ospita/Ospita-000001-flat.vmdk?dcPath=AdsPmVmw&dsName=v37kRm%5f10K%5fVMFS02'
HTTP/1.1 404 Not Found
Date: Mon, 5 Sep 2016 15:14:21 GMT
Set-Cookie: vmware_soap_session="52da2e5f-86e9-b035-bf39-8ca05761e6db"; Path=/; HttpOnly; Secure;
Connection: close
Content-Type: text; charset=plain
X-Frame-Options: DENY
Content-Length: 0

virt-v2v: error: vcenter: URL not found:
https://10.1.1.246/folder/Ospita/Ospita-000001-flat.vmdk?dcPath=AdsPmVmw&dsName=v37kRm%5f10K%5fVMFS02

The '--dcpath' parameter may be useful.  See the explanation in the
virt-v2v(1) man page OPTIONS section.

If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:

  virt-v2v -v -x [...]


Reading the man page I followed the dcpath option instructions, so I opened a browser with the vcenter ip, manually checking the dcpath and the complete guest path.
I verified that for some reason curl is trying to get the file Ospita-000001-flat.vmdk, but it does not exist!!
I attach the web screenshot, you can clearly see that file does not exist.
Can you give any advice please?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: