+++ This bug was initially created as a clone of Bug #1879969 +++ Description of problem: When importing a VMware VM from a cluster named "New Cluster", the migration failed. The virt-v2v log (attached) shows the following messages: 2020-09-16 16:08:54,020 - root - ERROR - virt-v2v error: could not parse '-ic vpx://administrator%40vsphere.local.net/Datacenter/host/New Cluster/vmware7.ciolab.net?no_verify=1'. Original error message was: parse_uri: unable to parse URI 2020-09-16 16:08:54,021 - root - DEBUG - b"virt-v2v: error: could not parse '-ic \n" 2020-09-16 16:08:54,022 - root - DEBUG - b'vpx://administrator%40vsphere.local.net/Datacenter/host/New \n' 2020-09-16 16:08:54,022 - root - DEBUG - b"Cluster/vmware7.ciolab.net?no_verify=1'. Original error message was: \n" 2020-09-16 16:08:54,022 - root - DEBUG - b'parse_uri: unable to parse URI\n' After renaming the cluster to "NewCluster", the import succeeded. It seems that the white space is not encoded as "%20" which leads virt-v2v to consider it as another argument, no a part of the URL. Version-Release number of selected component: 4.5.8 --- Additional comment from Fabien Dupont on 2020-09-17 13:21:08 UTC --- @Tomas, do you think this can be fixed in 4.5.z? --- Additional comment from Tomas Jelinek on 2020-09-17 13:30:28 UTC --- yes, let me target it to 4.6 and clone to 4.5
Verified on latest 4.5.z, from Oct 30 2020. VM import from VMware, when VMware cluster name is "New Cluster" ends up successfully.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5.17 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4325