Thanks for the report and the great description. The rationale here makes sense to me, and I agree with updating the packages in order to solve the described issue. However, since we will have to SRU this into Focal and Bionic (and I've just noticed that Hirsute's nfs-server.service file is basically the same as the one shipped in Focal, so we will have to this there as well), it would be really good to come up with a reproducer that can ideally be run in a VM (lxd, multipass, virt-manager, it doesn't matter).
I did a quick test here and fired up two LXDs VMs. I configured nfs- server in one of them, and placed the following in its /etc/exports: /testshare nfs-utils-bug1918141-focal-2.lxd(rw,sync,no_subtree_check) I verified that nfs-utils-bug1918141-focal-2.lxd can be resolved and is not in /etc/hosts, and then restarted the VM. It came back up right away, and the nfs-server service had been started successfully. I fiddled a bit with the systemd services, even created one fake service that just sleeps for a certain amount of time, but I guess that in a VM if network.target is up then you can just use the network right away. Anyway, if you have any ideas on how to reproduce this, I'm all ears. Otherwise, if it's really something hard to do in a VM, then we might just go ahead with the SRU and explain the situation. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
