Opening a task on systemd as well for this. When called early in boot, mount.nfs may fail because of any number of problems with the network. In this case, it appears it's being called by systemd before /etc/resolv.conf has been set up, resulting in a temporary DNS failure. There is no way for mount.nfs to work when invoked at this point in the boot.
So either systemd needs to more finely control the timing of the mount call so that it definitely happens only after the network is up (including /etc/resolv.conf configuration), or it needs to handle retrying the mount in the case of a temporary failure. (The latter is what mountall did in Ubuntu 14.10 and earlier.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515446 Title: NFS shares in FSTAB no longer mount at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1515446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
