No, nfs-kernel-server isn't failing to *start*; the "access denied" from
the bug description contradicts this. All signs point to this being a
race caused by nfs-kernel-server starting before DNS is available
(because the network isn't up yet), causing hostnames in the config to
fail to resolve.
It's true that ifupdown hasn't regressed vs. how we were starting
runlevel 2 before, but it's still buggy, because classically init
scripts in runlevel 2 are allowed to assume that the network is fully up
before they're called. When we changed this to only wait for lo, it was
a compromise because we hadn't worked out a way to keep the boot from
hanging forever in the case of problems. Now that we have a way to do
that, we should use it, deferring the static-network-up event until at
least one non-loopback interface is up even when all interfaces are
managed by NM. No additional delay if the network config actually *is*
static, and more robust handling of init scripts if it isn't.
(Clint, I've assigned this bug back to you as part of the reassignment
to ifupdown, but if this isn't on your priority list, feel free to
unassign... or assign it to one of your colleagues :)
** Package changed: nfs-utils (Ubuntu) => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848823
Title:
nfs-kernel-server requires a real interface to be up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/848823/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
