[Bug 893292] [NEW] Linux-3.0.0-13 upgrade breaks networking + simple temporary fix

[David Favor]

Public bug reported:

Upgrading Ubuntu-11.10 from kernel-3.0.0-12 to kernel-3.0.0-13 breaks
networking, rendering machines unbootable.

Problem is missing /run/network directory reported when
'/etc/init.d/networking restart' is run manually.

Multiple problems...

1) /etc/init/networking.conf creates /var/run/network instead of
/run/network

2) /run/network never populated

Fix seems to be changing /etc/init/networking.conf as follows:

1) change mkdir -p /var/run/network to /run/network

2) exec /etc/network/if-up.d/upstart to populate /run/network

/etc/network/if-up.d/upstart is what's called in /etc/init.d/networking to populate /run/network,
so that's what's used in this fix. There may be a more correct way to do this.

This doesn't work though, as it appears tmpfs gets mounted over
/run/network after networking.conf runs.

For now, adding the following big, ugly, simple hack to /etc/rc.local

mkdir -p /run/network && /etc/init.d/networking restart

** Affects: ifupdown (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- Linux-3.0.0-13 upgrade breaks networking + simple temporary fixroot
+ Linux-3.0.0-13 upgrade breaks networking + simple temporary fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/893292

Title:
  Linux-3.0.0-13 upgrade breaks networking + simple temporary fix

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  Upgrading Ubuntu-11.10 from kernel-3.0.0-12 to kernel-3.0.0-13 breaks
  networking, rendering machines unbootable.

  Problem is missing /run/network directory reported when
  '/etc/init.d/networking restart' is run manually.

  Multiple problems...

  1) /etc/init/networking.conf creates /var/run/network instead of
  /run/network

  2) /run/network never populated

  Fix seems to be changing /etc/init/networking.conf as follows:

  1) change mkdir -p /var/run/network to /run/network

  2) exec /etc/network/if-up.d/upstart to populate /run/network

  /etc/network/if-up.d/upstart is what's called in /etc/init.d/networking to populate /run/network,
  so that's what's used in this fix. There may be a more correct way to do this.

  This doesn't work though, as it appears tmpfs gets mounted over
  /run/network after networking.conf runs.

  For now, adding the following big, ugly, simple hack to /etc/rc.local

  mkdir -p /run/network && /etc/init.d/networking restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/893292/+subscriptions