Comment 13 for bug 1566508

>5. The issue being subject of this bug report is very likely still present, though I was unable to
>reproduce it exactly. Unfixed issue #2 caused auto fs to fail with a different error message
>("setautomntent: lookup(sss): setautomntent: No such file or directory"), while fixed issue #2 hid
>the bug. The workaround involving waiting for sssd to start listening on /var/lib/sss/pipes/autofs
>can still be used for extra safety.

Just for completeness, there are two different bugs going on:

- SSSD set as started before the responders are up, having AutoFS trying to connect to them ("setautomntent: lookup(sss): setautomntent: No such file or directory"). This has been reported at https://fedorahosted.org/sssd/ticket/3080

- SSSD trying to connect to its providers (LDAP, for instance) before the network is ready. This is the case you have detailed here, and is covered by Jakub's patches.

In my tests Xenial/Systemd can hit both of them, while Trusty/Upstart hits just the first one.