Bug 1311772

Description of problem: import vmware fail because curl is malformed.


Version-Release number of selected component (if applicable):
Node: oVirt Node Hypervisor release 3.6 (0.999.201602221022.el7.centos)
engine: ovirt-engine-3.6.2.6-1.el6.noarch
Vsphere 5.5


How reproducible: I tried import vm from v2v integrate (external provider) and I can see the list of shutdown vm's, but the start import process it fail with the next message on the node:

Feb 24 22:19:45 nodo journal: vdsm root ERROR Job u'4236f3cf-4401-519b-6e8f-332678a70ae5' failed#012Traceback (most recent call last):#012  File "/usr/share/vdsm/v2v.py", line 415, in _run#012    self._import()#012  File "/usr/share/vdsm/v2v.py", line 451, in _import#012    self._proc.stderr.read(1024)))#012V2VProcessError: Job u'4236f3cf-4401-519b-6e8f-332678a70ae5' process failed exit-code: 1, stderr: curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.xx.9.xx/folder/NAMEX/NAMEX-flat.vmdk?dcPath=Datacentername/Clustername&dsName=Datastorename'#012HTTP/1.1 404 Not Found#015#012Date: Wed, 24 Feb 2016 22:00:47 GMT#015#012Set-Cookie: vmware_soap_session="52f10bd7-0297-5061-5a73-41a61aa3bec2"; Path=/; HttpOnly; Secure; #015#012Connection: close#015#012Content-Type: text; charset=plain#015#012Content-Length: 0#015#012#015#012virt-v2v: error: vcenter: URL not found: #012https://10.xx.9.xx/folder/NAMEX/NAMEX-flat.vmdk?dcPath=Datacentername/Clustername&dsName=Datastorename#012#012The '--dcpath' parameter may be useful.  See the explanation in the #012virt-v2v(1) man page OPTIONS section.#012#012If reporting bugs, run virt-v2v with debugging enabled and include the #012complete output:#012#012  virt-v2v -v -x [...]



Steps to Reproduce:
1.Import vm from vmware external provider
2. start the process of import
3. fail

Actual results: The import process is not possible.


Expected results: The successful import of vm.


Additional info: 
I test the url from the vcenter and the correct url is:
https://10.xx.9.xx/folder/NAMEX/NAMEX-flat.vmdk?dcPath=Datacentername&dsName=Datastorename

the cluster name is the cause of error.