Bug 1368162

Summary: [Ansible Tower] No flash message when provided bad credentials
Product: Red Hat CloudForms Management Engine Reporter: John Prause <jprause>
Component: UI - OPSAssignee: lgalis
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, hkataria, jhardy, mmojzis, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: Regression, ZStream
Target Release: 5.6.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:tower
Fixed In Version: 5.6.3.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1366468 Environment:
Last Closed: 2016-11-30 19:52:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1366468    
Bug Blocks:    

Comment 1 CFME Bot 2016-11-03 20:41:13 UTC 
New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/0c23b6985f1bf72e21c80ce38ddfbd357b2e14d0

commit 0c23b6985f1bf72e21c80ce38ddfbd357b2e14d0
Author:     Dan Clarizio <dclarizi>
AuthorDate: Fri Oct 21 11:56:57 2016 -1000
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Thu Nov 3 16:36:20 2016 -0400

    Merge pull request #10683 from lgalis/ansible_add_provider_with_invalid_credentials
    
    Ansible Tower provider url verification does not display flash error with invalid credentials or when the URL contains a space
    (cherry picked from commit ec20ea90df7c53ae6dd396529b60194887889d04)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1368162

 app/views/provider_foreman/_form.html.haml | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)
Comment 2 Matouš Mojžíš 2016-11-15 10:52:26 UTC 
Verified in: 5.6.3.0. When I add wrong credentials it tells me: "Credential validation was not successful: Invalid username/password".
Comment 4 errata-xmlrpc 2016-11-30 19:52:51 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://rhn.redhat.com/errata/RHSA-2016-2839.html