As mentioned in the description, Autofs starts before SSSD's responders are running, even though SSSD is set to start before Autofs, both in upstart and systemd. The problem is related to the boot process of SSSD because upstart/systemd determine the job as started right after sssd forks, when in reality it's still starting the providers and responders that other services (e.g. autofs) might require.
Regarding AutoFS's required start: if AutoFS starts before SSSD, it'll have an empty mapping table. Once SSSD is running AutoFS will populate it, but only the indirect maps would be applied. According to its man page: Direct maps require a HUP signal be sent to the daemon to refresh their contents as does the master map. In previous releases, SSSD delayed the creation of its pidfile to address this issue (https://git.fedorahosted.org/cgit/sssd.git/commit/?id=d19c4785215305e6eb5f2fa2fc503a2ba50d3f10). I'll try to bring this back and experiment with the results. I'm going to provide a different workaround based on sssd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566508 Title: autofs races with sssd on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1566508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
