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

Bug #893292 reported by David Favor
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Expired
Undecided
Unassigned

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

David Favor (davidfavor)
summary: - Linux-3.0.0-13 upgrade breaks networking + simple temporary fixroot
+ Linux-3.0.0-13 upgrade breaks networking + simple temporary fix
Revision history for this message
David Favor (davidfavor) wrote :

To clarify... Machine booted fine @ Kernel 3.0.0-12 and upgrade only installed Kernel 3.0.0-13 packages.

This is odd as the problem occurs in the netbase package and no netbase or upstart package updates occurred.

My guess is something has changed in the way tmpfs mounting occurs... maybe...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ifupdown (Ubuntu):
status: New → Confirmed
Revision history for this message
Preston Wiley (preston-u) wrote :

I had this problem when upgrading from 11.04 to 11.10. The temporary fix to the rc.local file works around the problem, but it is added around 2 minutes to the boot time of the system.

Revision history for this message
Stéphane Graber (stgraber) wrote :

I'm sorry but I can't find anything wrong in our scripts... /var/run is a symlink to /run so whatever we end up using as mkdir target will work.

As for the two minutes comment, that's because since 11.10, we wait for all entries in /etc/network/interfaces to be configured, please check /etc/network/interfaces for any invalid configuration.

Also ensure that /run exists and is mounted as tmpfs (by initrd) and that /var/run is a symlink pointing to /run. If that's not the case, then this bug should be moved to the initscripts package instead.

Changed in ifupdown (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ifupdown (Ubuntu) because there has been no activity for 60 days.]

Changed in ifupdown (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.