#1886 If previous SRV query failed, the next try might not be retried in some cases
Closed: Fixed None Opened 5 years ago by jhrozek.

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.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta

Fields changed

milestone: SSSD 1.10 beta => SSSD 1.10.0

This is affecting production environments.

priority: major => critical

Fields changed

changelog: =>
owner: somebody => pbrezina
status: new => assigned

Fields changed

patch: 0 => 1

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A, just a bugfix

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.10.0

2 years ago

Login to comment on this ticket.

Metadata