Bug 1907940 - VMware CR not shown on MTV UI when incorrect password is provided while adding provider
Summary: VMware CR not shown on MTV UI when incorrect password is provided while addin...
Keywords:
Status: CLOSED DUPLICATE of bug 1907926
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: User Experience
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Fabien Dupont
QA Contact: Aziza Karol
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-15 14:46 UTC by Nandini Chandra
Modified: 2021-06-24 20:44 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 23:09:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nandini Chandra 2020-12-15 14:46:41 UTC
Description of problem:
-----------------------
When incorrect password is provided while adding VMware provider, provider CR is not listed on the MTV UI.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Add VMware provider with incorrect password
2.
3.

Actual results:
--------------
1)Provider CR is not listed on the MTV UI.
2)Snippet from provider yaml file
  status:
  conditions:
    - category: Required
      lastTransitionTime: '2020-12-15T00:56:59Z'
      message: >-
        Connection test, failed: ServerFaultCode: Cannot complete login due to
        an incorrect user name or password.
      reason: Failed
      status: 'False


Expected results:
----------------
1)Provider CR should be listed on the MTV UI so that user could update the provider with the correct password.
2)The status from the provider yaml file should be propagated to the provider advisory/status column on the MTV UI.



Additional info:
-----------------

Comment 1 Nandini Chandra 2020-12-17 23:09:31 UTC
Closing as a duplicate of

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


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