Bug 1543007 - VMRC authentication validation is required, if mistakenly RHV provider type is chosen at first
Summary: VMRC authentication validation is required, if mistakenly RHV provider type i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: Martin Maroši
QA Contact: Parthvi Vala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-07 14:59 UTC by Ilanit Stein
Modified: 2019-12-12 13:34 UTC (History)
12 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:33:48 UTC
Category: Bug
Cloudforms Team: VMware
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
cfme logs (339.14 KB, application/zip)
2018-02-07 15:15 UTC, Ilanit Stein
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:34:07 UTC

Description Ilanit Stein 2018-02-07 14:59:45 UTC
Description of problem:
When adding a VMware provider, if by mistake RHV provider is chosen,
after pressing "validate", and it fails (as expected since it is a wrong provider type), the provider type is chnaged to VMware, however at this stage the VMRC validation becomes required, and it is not possible to add the provider
(Add button is grayed out).

For a "regular" flow: When adding a VMware provider, with choosing from the beginning the correct provider, VMRC validation is not required.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ilanit Stein 2018-02-07 15:15:23 UTC
Created attachment 1392724 [details]
cfme logs

Comment 3 Ilanit Stein 2018-02-07 15:18:07 UTC
Comment on attachment 1392724 [details]
cfme logs

@16:42 - The VMware provider add trial with type: RHV.
@16:46 the VMware provider was added from new, with type VMware successully.

Comment 6 Ilanit Stein 2019-02-25 06:47:58 UTC
This bug reproduces on: 5.9.7.2.20190109154935_c0d03d6
and 5.10.1.1.20190212171432_83eb777

Followed the steps in the description.

Note that after the provider type is changed to the correct one (VMware),
the validation succeeds,
however, the "Add" button is still grayed out, since "VMRC console" validation is required -
and this is exactly the bug:
When adding a VMware provider, without choosing provider type "RHV, at first (by mistake), 
"VMRC console" validation is __not__ required.

Comment 7 Parthvi Vala 2019-02-25 08:43:07 UTC
I was able to replicate this BZ.

Steps taken to reproduce:
1. Add provider name and select RHV provider.
2. Add hostname and credentials for VMWare provider.
3. Validation will fail, and now change the provider to VMWare provider.
4. Validate the credentials. VMRC Console is now a required field and `Add` button is not validated.

Tested on 5.10.1.1.20190212171432_83eb777

Comment 9 Parthvi Vala 2019-03-06 06:42:34 UTC
Hi Harpreet,

I tested this on both 5.10.1.2 and 5.9.9.1 and I could still replicate the bug.
Can you check if the steps I mentioned to replicate this bug are correct? Check https://bugzilla.redhat.com/show_bug.cgi?id=1543007#c7

Thanks,
Parthvi

Comment 12 CFME Bot 2019-04-15 12:52:17 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/94659402d3401633c69dd26f65a61aa3585996e7
commit 94659402d3401633c69dd26f65a61aa3585996e7
Author:     Martin Marosi <marvusm.mmi>
AuthorDate: Wed Mar 13 06:42:53 2019 -0400
Commit:     Martin Marosi <marvusm.mmi>
CommitDate: Wed Mar 13 06:42:53 2019 -0400

    Swap ng-if with ng-show on VMRC Console in ems common.

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

 app/views/layouts/angular/_multi_auth_credentials.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 13 Parthvi Vala 2019-05-02 09:13:22 UTC
FIXED. Verified on 5.11.0.2.20190430174828_0e34dea.

Comment 15 errata-xmlrpc 2019-12-12 13:33:48 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/RHBA-2019:4199


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