Bug 1312504

Summary:	Inconsistent error message when host credential validation fails for RHEV and vCenter
Product:	Red Hat CloudForms Management Engine	Reporter:	Nandini Chandra <nachandr>
Component:	Providers	Assignee:	Greg Blomquist <gblomqui>
Status:	CLOSED WONTFIX	QA Contact:	Dave Johnson <dajohnso>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.4.0	CC:	dajohnso, hkataria, jfrey, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui:host:flash_msg
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-03 15:16:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nandini Chandra 2016-02-26 22:55:40 UTC

Description of problem:
----------------------


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


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


Steps to Reproduce:
------------------
1.Navigate to the host summary page.
2.Click 'Configuration', click 'Edit this item'.
3.Enter bad credentials.


Actual results:
--------------
The error message displayed is the not same for RHEV and vCenter hosts.
For vCenter, this is the message displayed.
 'Cannot complete login due to an incorrect user name or password.'
For RHEV,this is the error message displayed.
 'Login failed due to a bad username or password.'


Expected results:
----------------
For the sake of consistency, the error message should be the same.

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

Comment 2 Dave Johnson 2016-03-03 14:55:21 UTC

Pretty sure this is coming back straight from the provider...  maybe we could preface the error with '$provider API error: <message>' if we wanted to do something with this.

Comment 3 Greg Blomquist 2016-03-03 15:16:25 UTC

Dave, I was thinking the same thing.  We can look at normalizing these error messages.  But, at that point, we would have to probably wrap all these provider exceptions with MIQ exception types.

I probably see this as part of the larger "Provider Plugin" work.

At this point, I'm on the fence between closing this "wontfix" and just leaving it open to track it in respect to the bigger picture of wrapping provider errors with MIQ Exception types in Pluggable Providers.

----

Edit:

In Bug Triage today, we decided to close wontfix and reference this closed bug in the pluggable provider work.