Bug 1868737 - [UI][V2V][RHV to CNV VM import] Improve "API URL" structure info while connecting to new RHV instance
Summary: [UI][V2V][RHV to CNV VM import] Improve "API URL" structure info while connec...
Keywords:
Status: CLOSED DUPLICATE of bug 1850562
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Tomas Jelinek
QA Contact: Maayan Hadasi
URL:
Whiteboard: v2v
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-13 16:24 UTC by Maayan Hadasi
Modified: 2020-08-18 11:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-18 11:42:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Maayan Hadasi 2020-08-13 16:24:51 UTC
Description of problem:
In order to connect to new RHV instance, need to provide also "API URL" that match to this structure:
https://myengine.example.com/ovirt-engine/api
It is not clear enough that "API URL" should have the "https://" prefix 


Version-Release number of selected component (if applicable):
OpenShift 4.5.5
CNV 2.4.1


How reproducible:
100%


Actual results:
The user get informed that URL should end with "/ovirt-engine/api" while typing the field value
But it is not mentioned that the URL should start with "https://" 


Additional info:
This issue was found in OpenShift 4.5.5 after starting a VM import. The import failed with import error:

The virtual machine could not be imported.
ValidationFailed: Failed to initialize the source provider (Failed to connect to source provider): Post /ovirt-engine/sso/oauth/token: unsupported protocol scheme ""

Comment 1 Gilad Lekner 2020-08-18 11:39:18 UTC
this can be closed, https://github.com/openshift/console/pull/6290 fixes it

Comment 2 Yaacov Zamir 2020-08-18 11:42:37 UTC

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


Note You need to log in before you can comment on or make changes to this bug.