Bug 1884310

Summary: [v2v][VMware to CNV VM import] kubevirt-vmware crashes with https prefix
Product: Container Native Virtualization (CNV) Reporter: Filip Krepinsky <fkrepins>
Component: V2VAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Md Nadeem <mnadeem>
Severity: high Docs Contact:
Priority: high    
Version: 2.5.0CC: bthurber, cnv-qe-bugs, mnadeem, pkliczew
Target Milestone: ---   
Target Release: 2.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: v2.5.0-9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-17 13:24:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
v2v-vmware.log none

Description Filip Krepinsky 2020-10-01 16:11:45 UTC 
Created attachment 1718210 [details]
v2v-vmware.log

Description of problem:
The controller (v2v-vmware) crashes when trying to connect to vCenter with https protocol; for example: `https://vcenter.some.host.com`


Version-Release number of selected component (if applicable):
kubevirt-vmware v2.0.0-8


How reproducible:
100

Steps to Reproduce:
1. create a new connection to env with https:// prefix
2. vmware deployment crashes
3. kill the browser window so the cleanup doesn't appear

Actual results:

v2v-vmware deployment crashes and the VM Import Wizard is unusable

Expected results:
connection to vcenter is successful 



Additional info:
Comment 1 Md Nadeem 2020-10-23 12:51:48 UTC 
verified on CNV version : v2.5.0-333
Comment 4 errata-xmlrpc 2020-11-17 13:24:55 UTC 
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 Virtualization 2.5.0 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/RHEA-2020:5127