Learn more about these different git repos.
Other Git URLs
If a SRV query is attempted after the previous resolution if this query failed, but before the retry timeout, the next server is not even retried.
Code-wise this is because the failover request returns EIO and a NULL server and the be_fo_ request above gets trapped by this condition:
587 /* mark server as bad and retry */ 588 if (!state->srv) { 589 return EFAULT; 590 }
I think the failover request should return the SRV "meta-server" even if it wasn't retried so the caller can mark it as bad.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=954275 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=954275 954275]
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
milestone: SSSD 1.10 beta => SSSD 1.10.0
This is affecting production environments.
priority: major => critical
changelog: => owner: somebody => pbrezina status: new => assigned
patch: 0 => 1
resolution: => fixed status: assigned => closed
changelog: => N/A, just a bugfix
Metadata Update from @jhrozek: - Issue assigned to pbrezina - Issue set to the milestone: SSSD 1.10.0
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/2928
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.
Log in to comment on this ticket.