Bug 1849527 - [v2v] [api] VM import RHV to CNV importer should stop send requests to RHV if they are rejected because of wrong user/pass
Summary: [v2v] [api] VM import RHV to CNV importer should stop send requests to RHV i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.4.0
Assignee: Moti Asayag
QA Contact: Amos Mastbaum
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-22 06:33 UTC by Amos Mastbaum
Modified: 2020-07-28 19:10 UTC (History)
6 users (show)

Fixed In Version: v2.4.0-18
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 19:10:33 UTC
Target Upstream Version:
Embargoed:
amastbau: needinfo+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt vm-import-operator pull 310 0 None closed Do not requeue new request if provider init failed 2020-07-14 14:10:31 UTC
Red Hat Product Errata RHSA-2020:3194 0 None None None 2020-07-28 19:10:48 UTC

Description Amos Mastbaum 2020-06-22 06:33:52 UTC
Description of problem:
when running VM import from RHV to CNV, if the provider's (RHV) credentials in the secret are rejected by the provider, the importer will keep trying and that might lock the user in RHV 



Version-Release number of selected component (if applicable):


How reproducible:

Set RHV to lock a user after too many attempts.

Steps to Reproduce:
1.using the cli, create a secret with wrong password and than create the importer.


Actual results:

The Importer will keep trying to connect to RHV


Expected results:

The importer should not try again if the request is rejected with wrong user/password.

If this cannot be fix/changes,

**Need to add to the documentation a link to the RHV unlock user procedure.



Additional info:
The UI has similar  behavior after clicking "Check&Save".

Comment 1 Piotr Kliczewski 2020-06-22 14:55:41 UTC
We should fail the import if the credentials are not correct.

Comment 2 Dan Kenigsberg 2020-07-02 07:26:09 UTC
Amos, why is this report private? Unless it refers to private customer data or a security vulnerability, a bug report should be public.

Comment 3 Amos Mastbaum 2020-07-07 13:24:10 UTC
Verified api behavior only

Comment 6 errata-xmlrpc 2020-07-28 19:10:33 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, 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/RHSA-2020:3194


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