Created attachment 1703292 [details] v2v-vmware deployment fail screenshot Description of problem: In VM import wizard, deployment of VMware controller v2v-vmware will fail, if the VMware URL contains a space at the end. $ oc logs v2v-vmware-6f54d8b584-bxtks ... panic: parse https://10.1.41.37%20/sdk: invalid URL escape "%20" [recovered] panic: parse https://10.1.41.37%20/sdk: invalid URL escape "%20" ... Version-Release number of selected component (if applicable): OCP-4.5/CNV-2.4 How reproducible: 100%
Created attachment 1703293 [details] v2v-vmware.log
the validation should be fixed both on frontend and backend. Created a new BZ for the backend part: https://bugzilla.redhat.com/show_bug.cgi?id=1867980
Verified in CNV 2.5 Verified that the following error message is displayed when the 'vCenter hostname' contains any space whether it's in the beginning, middle or end. "Hostname must not contain white spaces"
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.6 GA Images), 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:4196