there was a customer complaining about fail over not reconnecting as
fast with sssd-1-13 as it did with sssd-1-14. The issue they were seeing
was that if sssd was offline, but the server came back up, it still took
sssd the full offline timeout cycle to attempt to reconnect, even though
we say that auth attempts are always done against the server.
I traced it to the difference in handling the offline state in the
providers themselves. With sssd-1-14, the only place that decides
whether to contact the providers is the DP itself. If the fast flag is
set and the provider is offline, we always return the offline error, if
the fast flag is unset, we ask the provider.
Now, the difference is that in sssd-1-13, we also have this code:
that would shortcut the request w/o trying to connect if the back end
was offline. I think this code is wrong and what sssd-1-14 does is
Therefore, I would like to just nuke the code that checks if the back
end is offline from the providers and let them always reconnect -- but
I'm not sure if this is safe to do in the LTM branch. In theory, laptop
users could complain about too frequent reconnects, however, I haven't
seen any complains with sssd-1-14 so far.