https://bugzilla.redhat.com/show_bug.cgi?id=710994
Description of problem: Getting ldap.OPERATIONS_ERROR: {'info': "Can't contact LDAP server", 'desc': 'Operations error'} while executing attached python script. This problem encountered while testing https://bugzilla.redhat.com/show_bug.cgi?id=640854. Steps: 1. Execute the attached python script. 2. You will see the errors: setup c1 to chain to ldap://localhost.localdomain:1200 localhost.localdomain:1210/ bind to c1 as uid=scarter turn on error logging on c1 shutdown m1 - see if still can search Traceback (most recent call last): File "bug628791.py", line 98, in <module> userc1.search_s(userdn, ldap.SCOPE_BASE) File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 516, in search_s return self.search_ext_s(base,scope,filterstr,attrlist,attrsonly,None,None,timeout=sel f.timeout) File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 510, in search_ext_s return self.result(msgid,all=1,timeout=timeout)[1] File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 436, in result res_type,res_data,res_msgid = self.result2(msgid,all,timeout) File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 440, in result2 res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout) File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 446, in result3 ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout) File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 96, in _ldap_call result = func(*args,**kwargs) ldap.OPERATIONS_ERROR: {'info': "Can't contact LDAP server", 'desc': 'Operations error'}
The problem is that chaining failover doesn't take effect until the next operation after the failure.
batch update moving tickets to future
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @rmeggins: - Issue set to the milestone: FUTURE
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/192
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.