+++ This bug was initially created as a clone of Bug #1850221 +++
Description of problem:
In UI, VM import wizard:
When entering some random text to RHV URL, ca certificate, user, password,
Clicking check & save button
Displays in the bottom of the wizard window:
"Connection successful. Loading data"
and then it is replaced with this message:
"Connection succeeded but could not read list of virtual machines from the RHV API instance"
This message is misleading, since the connection could not succeed with just random letters provided as RHV connection details.
Version-Release number of selected component (if applicable):
There should be a message saying connection to RHV failed.
--- Additional comment from Piotr Kliczewski on 2020-06-24 07:04:20 UTC ---
Based on code errors provided by ovirtsdk we are unable to distinguish whether we failed due to incorrect url, credentials or cert.
We need to come up with generic connection failure message.
--- Additional comment from Filip Krepinsky on 2020-06-24 09:58:23 UTC ---
The UI is just using the CR statuses which says LoadingVmsListFailed. Not sure we can do much about it there.
*** Bug 1850221 has been marked as a duplicate of this bug. ***
There has been a big batch of v2v related bugs moved to kubevirt plugin at once. We are working on them but due to capacity this did not make it last sprint.
I do not see this confusing message in the backend. I think we should only show "Loading data" which would end up as "Failed to load data"
ok, let's make the LoadingVmsListFailed status more generic so it will have the same meaning as Failed status
I am unable to reproduce this bug. Yaacov, could you please try to reproduce and let me know if you are able to do so?
well, some of this bug's symptoms are gone :-)
but not all, we still get the string "Connection succeeded" even if connection did not succeeded,
the fixes in other bugs that fixes part of this problem didn't solve the root cause of this,
witch is the UI assuming the connection was successful, when it should just report the message it's getting form the backend.
to see this behaviour:
a. start the vm-import
b. fill in correct logging in information for a rhev instance
c. change the user name to a none valid user
check connection, the connection should fail because the user name is not valid, but the message we get is saying "Connection successful"
Created attachment 1713409 [details]
connection successful message for bad user name error
moving out until there is a lgtm on the patch
Now the message is different:
“Connection failed. Please check your credentials and ensure that the API you're attempting to connect to is operational.”
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.