Bug 1468252 - Incorrect error message when trying to login to appliance with 'web services' role disabled
Summary: Incorrect error message when trying to login to appliance with 'web services'...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: Martin Hradil
QA Contact: Antonin Pagac
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-06 13:14 UTC by luke couzens
Modified: 2019-02-07 23:02 UTC (History)
11 users (show)

Fixed In Version: 5.10.0.15
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:02:36 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:02:47 UTC

Description luke couzens 2017-07-06 13:14:35 UTC
Description of problem:Incorrect error message when trying to login to appliance with 'web services' role disabled


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


How reproducible:100%


Steps to Reproduce:
1.provision 2 appliances
2.configure first appliance
3.join region with second appliance
4.login to first appliance ui
5.nav to configuration-settings
6.select second appliance
7.disable web services role
8.connect to webui of second appliance
9.try to login

Actual results:Error message 'Incorrect username or password' 


Expected results:

Firstly if the web services role is disabled should we even be able to hit the webui of that appliance?

If we can, then we should see a new page informing the user that web services have been disable for this host. 

Either way the error message shown when trying to login states incorrect credentials but this is not the issue here, so just a correction to the error message could also be useful.


Additional info:

Comment 3 Joe Vlcek 2018-08-27 17:39:57 UTC
Luke,

Is this still an issue? A lot of improvements have been made in this space since you originally reported it.

Please confirm if it is still happening.

Thank you, JoeV

Comment 14 CFME Bot 2018-09-06 06:19:55 UTC
New commits detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/0aa9f5b0d95a4cd97ed2d7b1ee9c0167d4a3ea3d
commit 0aa9f5b0d95a4cd97ed2d7b1ee9c0167d4a3ea3d
Author:     Martin Hradil <mhradil>
AuthorDate: Wed Sep  5 10:38:37 2018 -0400
Commit:     Martin Hradil <mhradil>
CommitDate: Wed Sep  5 10:38:37 2018 -0400

    Login - flash statusText instead of "Incorrect username or password"

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1468252

 app/assets/javascripts/miq_application.js | 9 +-
 1 file changed, 7 insertions(+), 2 deletions(-)


https://github.com/ManageIQ/manageiq-ui-classic/commit/7317ef49cdaaea6417e6576169d65d60c7c23bb0
commit 7317ef49cdaaea6417e6576169d65d60c7c23bb0
Author:     Martin Hradil <mhradil>
AuthorDate: Wed Sep  5 10:40:29 2018 -0400
Commit:     Martin Hradil <mhradil>
CommitDate: Wed Sep  5 10:40:29 2018 -0400

    API.login - don't show popup on 503

    means any caller of API.login needs to be able to deal with 503 Service Unavailable

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

 app/javascript/http_api/api.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 15 Antonin Pagac 2019-01-14 12:29:22 UTC
Verified with 5.10.0.31.

The error message now reads: "Login failed: Service Unavailable". Works as expected.

Comment 16 errata-xmlrpc 2019-02-07 23:02:36 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-2019:0212


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