Comment 9 for bug 1918141

I'm not sure it's *ever* correct for distribution packaging to ship After=network-online.target. One person's "wait for the network to come online" is another person's "my system hangs on boot because I'm booting offline" and yet another person's "one NIC was up but the one through which DNS is available was not so doing this didn't work anyway". See also: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/, all bugs I've been tagging network-online-ordering, and today I also came across https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878109 which describes the same issue. This means I'm also questioning the "fix" in Hirsute. This seems to run completely contrary to upstream's recommendations as linked above.

> Our workaround is to add the appropriate dependecies in /etc/systemd/system/nfs-server.service.d/dependencies.conf...

I believe this is the correct thing to do, but rather than a workaround it's simply configuring the service to your local requirements. We cannot predict all differing local requirements in packaging in advance, especially when they can conflict in practice.

In general, should all network-type services in Ubuntu be After=network-online.target, or not? I think this is a question we should answer for the entire distribution at once, rather than pushing piecemeal changes that lead to inconsistency and confusion. So -1 for the SRU until we have consensus, and I suggest reverting the change in Hirsute in the meantime also.