Bug 974148 - RHEV-M AD authentication does not work if one of the DCs is defunct.
RHEV-M AD authentication does not work if one of the DCs is defunct.
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
All Linux
high Severity high
: ---
: 3.3.0
Assigned To: Martin Perina
Ondra Machacek
Depends On:
Blocks: 1019461
  Show dependency treegraph
Reported: 2013-06-13 10:08 EDT by Roman Hodain
Modified: 2016-02-10 14:28 EST (History)
11 users (show)

See Also:
Fixed In Version: is7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 12:27:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 16859 None None None Never
Red Hat Product Errata RHSA-2014:0038 normal SHIPPED_LIVE Important: Red Hat Enterprise Virtualization Manager 3.3.0 update 2014-01-21 17:03:06 EST

  None (edit)
Description Roman Hodain 2013-06-13 10:08:51 EDT
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 08:21:41 EDT
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-27 19:15:16 EST
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:


Thanks in advance.
Comment 14 errata-xmlrpc 2014-01-21 12:27:23 EST
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.


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