#3009 sssd fails to mark a connection as bad on searches that time out
Closed: Fixed None Opened 5 years ago by tscherf.

In case you have multiple servers defined in sssd.conf, it might happen that no failover takes place. When a connection to one server can be established and port 389 is reachable, but when the ldap search times out, sssd does not mark the connection as bad and keeps talking to this server instead of failing over to any of the other servers defined in the configuration.

Picking up since I have a candidate patch.

owner: somebody => jhrozek
status: new => assigned

The patch is on the list.

patch: 0 => 1

There is a patch and also a downstream bugzilla attached, therefore filing into 1.14

milestone: NEEDS_TRIAGE => SSSD 1.14 alpha

Bugfixes shouldn't block the Beta release.

milestone: SSSD 1.14 alpha => SSSD 1.14.0

Downstream BZ -> increase in priority.

priority: major => critical

1.14.0 should be released no later than Wednesday next week, this ticket should not block the 1.14.0 release.

There is a patch, though. Just need a review.

milestone: SSSD 1.14.0 => SSSD 1.14.1

resolution: => fixed
status: assigned => closed

Metadata Update from @tscherf:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.14.1

4 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/4050

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.