[Bug 1080975] [NEW] ifup fails on boot if initramfs already configured the device

[Stephen Warren]

Public bug reported:

I have a server with a static IP, so I put the following into
/etc/network/interfaces to configure it:

auto eth0
iface eth0 inet static
    address 192.168.63.152
    network 192.168.63.0
    netmask 255.255.255.0
    broadcast 192.168.63.255
    gateway 192.168.63.1

However, if the initramfs brought up that interface, then ifup fails to
bring it up (again). The error message was something like "NETLINK:
address already exists" if I ran "ifup eth0" after the system had booted
at least.

For the record, I have the following in /etc/initramfs-
tools/initramfs.conf:

DEVICE=eth0
IP=192.168.63.152::192.168.63.1:255.255.255.0:avon.wwwdotorg.org:eth0:off

... although I did try commenting out those two lines and rebuilding the
initramfs and it made no difference; I assume because eth0 was still
brought up, just with DHCP rather than a static IP.

This is a problem if I have a cryptoroot, and I've configured the
initramfs to bring up the network along with dropbear, so I can ssh in
and unlock the cryptoroot. In this case, after the root is unlocked,
mounted, and the "real" boot starts, ifup fails, and hence the static-
network-up upstart event is never emitted, and hence
/etc/init/failsafe.conf sleeps for 2 whole minutes before booting the
system completely, with is extremely annoying.

A hacky workaround is to edit e.g. /usr/share/initramfs-tools/scripts
/init-bottom/dropbear and add the following line right at the very end:

ifconfig eth0 0.0.0.0 down

Then, the system boots quickly.

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

-- 
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/1080975

Title:
  ifup fails on boot if initramfs already configured the device

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  I have a server with a static IP, so I put the following into
  /etc/network/interfaces to configure it:

  auto eth0
  iface eth0 inet static
      address 192.168.63.152
      network 192.168.63.0
      netmask 255.255.255.0
      broadcast 192.168.63.255
      gateway 192.168.63.1

  However, if the initramfs brought up that interface, then ifup fails
  to bring it up (again). The error message was something like "NETLINK:
  address already exists" if I ran "ifup eth0" after the system had
  booted at least.

  For the record, I have the following in /etc/initramfs-
  tools/initramfs.conf:

  DEVICE=eth0
  IP=192.168.63.152::192.168.63.1:255.255.255.0:avon.wwwdotorg.org:eth0:off

  ... although I did try commenting out those two lines and rebuilding
  the initramfs and it made no difference; I assume because eth0 was
  still brought up, just with DHCP rather than a static IP.

  This is a problem if I have a cryptoroot, and I've configured the
  initramfs to bring up the network along with dropbear, so I can ssh in
  and unlock the cryptoroot. In this case, after the root is unlocked,
  mounted, and the "real" boot starts, ifup fails, and hence the static-
  network-up upstart event is never emitted, and hence
  /etc/init/failsafe.conf sleeps for 2 whole minutes before booting the
  system completely, with is extremely annoying.

  A hacky workaround is to edit e.g. /usr/share/initramfs-tools/scripts
  /init-bottom/dropbear and add the following line right at the very
  end:

  ifconfig eth0 0.0.0.0 down

  Then, the system boots quickly.

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