Bug 1339939

Summary:	[RFE] Provide a mechanism to report which Active Directory domain controller is currently being queried
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Greg Scott <gscott>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	lsurette, mperina, oourfali, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-23 21:05:13 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:

Description Greg Scott 2016-05-26 08:47:43 UTC

Description of problem:

With the coming migration away from engine-manage-domains where the admin specifies the Kerberos server(s) or Windows Active Directory domain controllers to ovirt-engine-extensions-aaa-ldap where the admin uses DNS SRV records to find domain controller(s), RHEV needs a way to report which domain controllers it's using at any given time.

This is important for management and troubleshooting when login problems occur.  Is there a problem with a domain controller?  In order to answer this question, it's important to know **which** domain controller is in use.

This needs to be available to both the RHEVM GUI and Java and other APIs.

Comment 1 Yaniv Kaul 2016-05-26 10:19:50 UTC

I don't see how it can be done in the UI - or the API. Only in the engine.log it is feasible and makes sense.

Comment 2 Yaniv Kaul 2017-06-07 19:09:50 UTC

Martin, if it's in the engine.log, please close this RFE. If not, I'd be happy if we can implement it.

Comment 3 Martin Perina 2017-06-23 21:05:13 UTC

We have already added this information into log as a part of BZ1353750

*** This bug has been marked as a duplicate of bug 1353750 ***