I tested sssd-1.13.4-1ubuntu1.4 on xenial on a bare metal machine equipped with Intel X550T, a network controller notorious for long and somewhat random startup initialization time. I am happy to report that autofs boot problems still occur, but at a much diminished rate. While previously autofs was failing at nearly every boot, now I observed only one failure in 50 tries. I believe that this improvement comes from "autofs.service" being added to "Before" line in sssd.service file (a change introduced in sssd-1.13.4-1ubuntu1.4). When I removed this modification, autofs tended to start before sssd, and failed much more often with an error "setautomntent: lookup(sss): setautomntent: Connection refused". On the other hand, with the modification in place, the very occasional failures were accompanied with an error "setautomntent: lookup(sss): setautomntent: No such file or directory", which results from network interface coming online after sssd and autofs have already started. However, the topic of this bug is a race between sssd and autofs, and not the race between sssd and autofs on one side, and network initialization on the other (bug 1588915), even though effects are similar. Thus I would vote to consider this bug fixed.
-- 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/sssd/+bug/1566508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
