Learn more about these different git repos.
Other Git URLs
The retry time to resolve a SRV query again is the same for cases where the SRV resolution works fine and for cases where it doesn't. That's wrong I think, we should set a shorter retry interval for cases where the lookup fails. Typically this would not be a problem because the SSSD can either stick to the server that works or if none work, the client is usually really offline and going online (as a result of libnl callback) would reset the status.
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]
milestone: NEEDS_TRIAGE => SSSD 1.11 beta
Re-test as it might have been fixed by some other patch.
milestone: SSSD 1.13 beta => Interim Bucket
milestone: Interim Bucket => SSSD 1.12 beta
owner: somebody => preichl
patch: 0 => 1
resolution: => fixed
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12 beta
to comment on this ticket.