Bug 756528 - Backend: Exception thrown for Failed to query rootDSE for LDAP server
Summary: Backend: Exception thrown for Failed to query rootDSE for LDAP server
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-23 20:33 UTC by Dafna Ron
Modified: 2012-12-13 08:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-13 08:13:22 UTC
oVirt Team: ---


Attachments (Terms of Use)
log (300.88 KB, application/x-gzip)
2011-11-23 20:33 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2011-11-23 20:33:04 UTC
Created attachment 535632 [details]
log

Description of problem:

we need to clean the error message in rhevm log when when LDAP server selected is down and  we fail to get RootDSE

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

ic150

How reproducible:

100%

Steps to Reproduce:
1. stop one DC server
2. restart jboss and try to connect
3. 
  
Actual results:
 when we fail to get rootDSE from the server we get a long "messy" error in rhevm log

Expected results:

we should have a clean error

Additional info:full rhevm log

2011-11-23 22:21:58,608 ERROR [org.ovirt.engine.core.bll.adbroker.GetRootDSE] (pool-11-thread-1) Failed to query rootDSE for LDAP server LDAP://blackdc.qa.lab.tlv.redhat.com:389 due to blackdc.qa.lab.tlv.redhat.com:389
2011-11-23 22:21:58,608 ERROR [org.ovirt.engine.core.bll.adbroker.GetRootDSETask] (pool-11-thread-1) Couldnt deduce provider type for domain {0}
2011-11-23 22:21:58,613 ERROR [org.ovirt.engine.core.bll.adbroker.DirectorySearcher] (QuartzScheduler_Worker-1) Failed ldap search server LDAP://blackdc.qa.lab.tlv.redhat.com:389 due to org.ovirt.engine.core.bll.adbroker.RhevmDirectoryServiceException: Failed to get rootDSE record for server LDAP://blackdc.qa.lab.tlv.redhat.com:389. We should try the next server
org.ovirt.engine.core.bll.adbroker.RhevmDirectoryServiceException: Failed to get rootDSE record for server LDAP://blackdc.qa.lab.tlv.redhat.com:389
        at org.ovirt.engine.core.bll.adbroker.GetRootDSETask.call(GetRootDSETask.java:68)
        at org.ovirt.engine.core.bll.adbroker.DirectorySearcher$1.call(DirectorySearcher.java:101)
        at org.ovirt.engine.core.bll.adbroker.DirectorySearcher$1.call(DirectorySearcher.java:97)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:46)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
2011-11-23 22:22:19,918 ERROR [org.ovirt.engine.core.bll.adbroker.DirectorySearcher] (QuartzScheduler_Worker-1) Error in finding LDAP servers for domain dc.eng.lab.tlv.redhat.com
2011-11-23 22:22:33,604 ERROR [org.ovirt.engine.core.bll.adbroker.DirectorySearcher] (http-0.0.0.0-8443-1) Failed ldap search server LDAP://blackdc.qa.lab.tlv.redhat.com:389 due to org.ovirt.engine.core.bll.adbroker.RhevmDirectoryServiceException: Connection to to server has timed out.. We should try the next server
org.ovirt.engine.core.bll.adbroker.RhevmDirectoryServiceException: Connection to to server has timed out.
        at org.ovirt.engine.core.bll.adbroker.LdapSearchExceptionHandler.handleTimeout(LdapSearchExceptionHandler.java:105)
        at org.ovirt.engine.core.bll.adbroker.LdapSearchExceptionHandler.handle(LdapSearchExceptionHandler.java:25)
        at org.ovirt.engine.core.bll.adbroker.LdapSearchExceptionHandler.handle(LdapSearchExceptionHandler.java:17)
        at org.ovirt.engine.core.bll.adbroker.DirectorySearcher.find(DirectorySearcher.java:121)
        at org.ovirt.engine.core.bll.adbroker.DirectorySearcher.FindOne(DirectorySearcher.java:45)
        at org.ovirt.engine.core.bll.adbroker.LdapAuthenticateUserCommand.executeQuery(LdapAuthenticateUserCommand.java:44)
        at org.ovirt.engine.core.bll.adbroker.LdapBrokerCommandBase.Execute(LdapBrokerCommandBase.java:68)
        at org.ovirt.engine.core.bll.adbroker.LdapBrokerBase.RunAdAction(LdapBrokerBase.java:18)
        at org.ovirt.engine.core.bll.LoginUserCommand.AuthenticateUser(LoginUserCommand.java:36)
        at org.ovirt.engine.core.bll.LoginBaseCommand.canDoAction(LoginBaseCommand.java:186)
        at org.ovirt.engine.core.bll.LoginAdminUserCommand.canDoAction(LoginAdminUserCommand.java:20)
        at org.ovirt.engine.core.bll.CommandBase.InternalCanDoAction(CommandBase.java:396)
        at org.ovirt.engine.core.bll.CommandBase.ExecuteAction(CommandBase.java:203)

Comment 1 Itamar Heim 2011-11-24 07:03:52 UTC
log should remain for error (or warning) of course. just the stack trace has to go away (can keep it in debug if really like)

Comment 2 Itamar Heim 2012-12-13 08:13:22 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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