The message "setautomntent: lookup(sss): setautomntent: No such file or directory" is not indicative of any bug whasoever. It just means there are no more entries in this maps.
But in general, I think the most systematic way forward for this kind of startup races would be to socket-activate the responders and switch to let systemd manage all the responders. sssd should not try to be a service manager.
The message "setautomntent: lookup(sss): setautomntent: No such file or directory" is not indicative of any bug whasoever. It just means there are no more entries in this maps.
But in general, I think the most systematic way forward for this kind of startup races would be to socket-activate the responders and switch to let systemd manage all the responders. sssd should not try to be a service manager.