In order to test whether the bug which is the subject of this bug report (i.e. "no mounts in table", not "setautomntent") occurs in Xenial with systemd, I created autofs.service as attached below. This way I could dispense with /etc/init.d/autofs and directly control when autofs is started. I can report that I was unable to reproduce this bug. When autofs was configured to start after sssd, and sssd started after network was up, autofs mounted all shares as expected and no error messages were logged.
On the other hand, if both sssd and autofs started before network was up, shares would not be mounted, and syslog would contain an error message "setautomntent: lookup(sss): setautomntent: No such file or directory". If autofs was started before sssd, the error message would be "setautomntent: lookup(sss): setautomntent: Connection refused". Ensuring that network interfaces were up before systemd reached network.target and network-online.target was a pain in the neck and an exercise of frustration. But this is material for another bug report. -- 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
