Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1850231

Summary: [v2v][UI]VM import RHV to CNV: wrong error message when wrong ca certificates are provided
Product: OpenShift Container Platform Reporter: Ilanit Stein <istein>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED DUPLICATE QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, cnv-qe-bugs, yzamir
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1850583 (view as bug list) Environment:
Last Closed: 2020-06-24 14:17:00 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:
Bug Depends On:    
Bug Blocks: 1850583    

Description Ilanit Stein 2020-06-23 19:02:39 UTC 
Description of problem:
In UI, VM import wizard, when picking RHV provider, and providing correct connection details, except for ca certificate (deleted a raw from  

Version-Release number of selected component (if applicable):
CNV-2.4
vm-import-operator: quay.io/kubevirt/vm-import-operator:v0.0.3
vm-import-controller: quay.io/kubevirt/vm-import-controller:v0.0.3

This message is displayed:
"Can not verify RHV API credentials, connection to the OvirtProvider failed."

Though RHV credentials (user/password) are correct.
The ca certificate is wrong.
Comment 1 Piotr Kliczewski 2020-06-24 07:09:04 UTC 
In this specific case we got handshake error. We should display a generic message that provided connection information is not correct.
Comment 2 Yaacov Zamir 2020-06-24 14:17:00 UTC 
Moving to Console Kubevirt Plugin

https://bugzilla.redhat.com/show_bug.cgi?id=1850583

FYI:
@Nelly @Piotr @Tomas @Ilanit @Filip

*** This bug has been marked as a duplicate of bug 1850583 ***