Description of problem:
When failing to contact the AD domain controller, the following event can be seen in the engine.log, which is missing the real cause:

"Failed to query rootDSE for LDAP server LDAP://qa2-tlv.qa.lab.tlv.redhat.com:389 due to qa2-tlv.qa.lab.tlv.redhat.com:389"

Part of the code relevant to this is probably

} catch (NamingException e) {
            log.errorFormat("Failed to query rootDSE for LDAP server {0} due to {1}", ldapURI, e.getMessage());

(from upstream's backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/adbroker/GetRootDSE.java)

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

How reproducible:


Steps to Reproduce:
1. Make sure the first AD domain controller you try to connect to does not respond, and try to login with a user from the AD domain to the system.
2.
3.
  
Actual results:


Expected results:


Additional info:
2012-10-10 09:30:37,888 INFO  [org.ovirt.engine.core.bll.adbroker.GetRootDSE] (ajp-/127.0.0.1:8702-3) Trying to auto-detect the LDAP provider type for domain qa.lab.tlv.redhat.com
2012-10-10 09:30:37,894 ERROR [org.ovirt.engine.core.bll.adbroker.DirectorySearcher] (ajp-/127.0.0.1:8702-2) Failed ldap search server LDAP://qa2-tlv.qa.lab.tlv.redhat.com:389 due to javax.naming.CommunicationException: qa2-tlv.qa.lab.tlv.redhat.com:389 [Root exception is java.net.SocketTimeoutException: connect timed out]. We should try the next server
2012-10-10 09:31:07,921 ERROR [org.ovirt.engine.core.bll.adbroker.GetRootDSE] (ajp-/127.0.0.1:8702-3) Failed to query rootDSE for LDAP server LDAP://qa2-tlv.qa.lab.tlv.redhat.com:389 due to qa2-tlv.qa.lab.tlv.redhat.com:389