Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1454811

Summary: [downstream clone - 4.1.5] No error pops when logging with a locked ovirt user account
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED ERRATA QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0.0CC: cfergeau, dblechte, grafuls, juzhou, kuwei, lsurette, mgoldboi, mperina, mxie, mzhan, oourfali, pstehlik, rbalakri, Rhev-m-bugs, rnori, sabose, srevivo, tzheng, virt-bugs, virt-viewer-maint, xiaodwan, ykaul
Target Milestone: ovirt-4.1.5Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1445681 Environment:
Last Closed: 2017-08-22 17:42:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1445681    
Bug Blocks:    

Comment 6 Gonza 2017-08-21 09:43:54 UTC 
Verified with:
ovirt-engine-4.1.5.3-0.0.master.20170815115046.git41c45b8.el7.centos.noarch

...
< HTTP/1.1 401 Unauthorized
< Date: Mon, 21 Aug 2017 09:17:23 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="RESTAPI"
< Content-Type: text/html;charset=UTF-8
< Content-Length: 216
< 
* Connection #0 to host 10-xxx.com left intact
<html><head><title>Error</title></head><body>access_denied: Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator..</body></html>%
Comment 8 errata-xmlrpc 2017-08-22 17:42:35 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/RHEA-2017:2509