#1101 LDAP failover not working if server refuses connections
Closed: Fixed None Opened 12 years ago by sgallagh.

When we switched our LDAP communication over to establishing the socket connection ourselves, we didn't account for all possible error codes from {{{connect()}}}. Currently, we will only fail over to the next server if ETIMEDOUT is returned.

We need to fail over on any error from {{{connect()}}}.


Fixed by:
- 0aaf73e (master)
- 11f9ae2 (sssd-1-6)
- e78c9b9 (sssd-1-5)

keywords: => Regression
milestone: NEEDS_TRIAGE => SSSD 1.5.16
patch: 0 => 1
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.16

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2143

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata