Learn more about these different git repos.
Other Git URLs
A server status in fail over is reset from "not working" to "unknown" after an interval, which is currently hardcoded to 30 seconds. This might be a problem when it takes a long time for individual server tries.
For example, the default krb5_child timeout is 15 seconds, so when there is more than 2 servers in the fail over chain, the first server is always reset to the "default" state when the back end completes a full cycle over the servers.
We should modify the fail over (or the be_fo_ wrapper) to only allow one full cycle over the server list.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=795562 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=795562 795562]
milestone: NEEDS_TRIAGE => SSSD 1.8.1 (LTM)
owner: somebody => jhrozek
priority: major => blocker
status: new => assigned
component: SSSD => Failover
patch: 0 => 1
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.8.1 (LTM)
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:
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.
to comment on this ticket.