Ok. If I'm not mistaken, this is a regression introduced by the switch
of rc-sysinit.conf from starting on 'network-interface-up IFACE!=lo' to
'static-network-up'. Previously, we had a guarantee that scripts in
runlevel 2 would not be started until at least one non-loopback
interface is up. Now, if there are *no* interfaces configured in
ifupdown (i.e., all networking is done via NM), the 'static-network-up'
event will be emitted as soon as the loopback interface itself comes up.
That means services such as nfs-kernel-server will try to start before
there's a route to the DNS server, resulting in exactly the failure you
describe here.
We need to fix this in ifupdown for release, so that we never emit
static-network-up until at least one non-loopback interface is brought
up. (And if none are brought up, we wait for the 'failsafe' event as
before.)
** Package changed: nfs-utils (Ubuntu) => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Importance: Medium => High
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Summary changed:
- mounting of nfs shares fails and must restart nfs-kernel-server
+ if all interfaces are configured via NM, static-network-up emitted when only
lo is configured
--
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:
if all interfaces are configured via NM, static-network-up emitted
when only lo is configured
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/848823/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
