Comment 14 for bug 1566508

Victor, you are right saying that we are dealing with more than one bug here. It appears to me that we have 3 or 4 separate bugs all conspiring to prevent autofs from starting in the configuration as described above. I think that the "setautomntent" error message is a symptom of a different bug than the one causing the "no mounts in table" error. I experienced both problems in Trusty/upstart, but so far only the "setautomntent" bug in Xenial/Systemd/autofs-with-SysV. According to my tests, the "setautomntent" bug is caused by sssd starting before network is ready, while "no mounts in table" results from sssd reaching ready state before its responders are up. However, Xenial startup is a total mess, and I am still trying to figure out what is really happening, so I may be wrong in the details.