Bug 974148

Summary:	RHEV-M AD authentication does not work if one of the DCs is defunct.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Roman Hodain <rhodain>
Component:	ovirt-engine	Assignee:	Martin Perina <mperina>
Status:	CLOSED ERRATA	QA Contact:	Ondra Machacek <omachace>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, bdagan, iheim, jkt, lpeer, lyarwood, mperina, pstehlik, Rhev-m-bugs, yeylon, yzaslavs
Target Milestone:	---
Target Release:	3.3.0
Hardware:	All
OS:	Linux
Whiteboard:	infra
Fixed In Version:	is7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 17:27:23 UTC	Type:	Bug
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:
Bug Blocks:	1019461

Description Roman Hodain 2013-06-13 14:08:51 UTC

Description of problem:
The admin portal is not able to authenticate the users from an Active Directory if one of the domain controllers is not reachable.

The registration and validation of the domain is Ok.

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

How reproducible:
100% in a specific configuration

Steps to Reproduce:
1. Register the RHEV-M to AD with two DCs
2. Turn off one of the DCs
3. Try to log in 

Actual results:
The user is not allowed to log in.

Expected results:
The user is allowed to log in.

Additional info:

Comment 11 Martin Perina 2013-07-15 12:21:41 UTC

The bug has already been partially resolved upstream. The only remaining error was in root DSE query code block: when the first LDAP server in list was not available, there was an uncaught RuntimeException that prevents querying next LDAP server and makes login unsuccessful at once.

Comment 13 Charlie 2013-11-28 00:15:16 UTC

This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 14 errata-xmlrpc 2014-01-21 17:27:23 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.

http://rhn.redhat.com/errata/RHSA-2014-0038.html