Network device not configured correctly

Bug #1046029 reported by Brad Figg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netcfg (Ubuntu)
New
High
Unassigned

Bug Description

This is not 100% reproducible. Sometimes the server comes up this way and other
times it comes up just as you'd expect with em2 properly configured and up.

This is a Quantal install on a Intel server.

Upon initial bootup of a server after provisioning via orchestra server I have no network device configured. My /etc/network/interfaces file looks like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto rename3
iface rename3 inet dhcp

This server has em1, em2, em3 and em4:

em1 Link encap:Ethernet HWaddr 60:eb:69:21:2c:6c
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1866 (0.0 B) TX bytes:0 (0.0 B)
          Memory:95b20000-95b40000

em2 Link encap:Ethernet HWaddr 60:eb:69:21:2c:6d
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Memory:95b00000-95b20000

em3 Link encap:Ethernet HWaddr 60:eb:69:21:2c:6e
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Memory:95a20000-95a40000

em4 Link encap:Ethernet HWaddr 60:eb:69:21:2c:6f
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Memory:95a00000-95a20000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1184 (1.1 KB) TX bytes:1184 (1.1 KB)

Tags: quantal
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :

$ dpkg -l | grep biosdevname

ii biosdevname 0.4.1-0ubuntu2 amd64 apply BIOS-given names to network devices

description: updated
Brad Figg (brad-figg)
description: updated
Revision history for this message
Colin Watson (cjwatson) wrote :

Thanks. My guess is that this is a race between netcfg and the biosdevname udev rules.

affects: debian-installer (Ubuntu) → netcfg (Ubuntu)
Changed in netcfg (Ubuntu):
importance: Undecided → High
tags: added: quantal
Revision history for this message
Marco CONSONNI (marco-consonni) wrote :

Hello,

I also faced this bug.
Is there some known workaround?
Thanks.

Revision history for this message
Jeremy Kitchen (kitchen-c) wrote :

also running into this bug and seeking a workaround.

Revision history for this message
Jeremy Kitchen (kitchen-c) wrote :

I found a workaround: fix the interface name afterward with nameif(8)

it's ugly, and I really hope this bug gets fixed some day, but at least I don't have to play reboot roulette and hope I get the correct device names.

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.