[Bug 678425] Re: alias network interfaces sometimes dont start on boot

[Launchpad Bug Tracker]

This bug was fixed in the package ifupdown - 0.7~beta2ubuntu1

---------------
ifupdown (0.7~beta2ubuntu1) precise; urgency=low

  * Resynchronise with Debian experimental.  Remaining changes
    (LP: #905660, LP: #850566, LP: #611877, LP: #678425):
    - ifupdown.nw: Use 100 as default route metric unless an explicit metric
      parameter is set in /etc/network/interface.
    - Add iniparser3.0b sources (dictionary.c, dictionary.h, iniparser.c,
      iniparser.h), to let ifupdown avoid auto-up/down of interfaces if
      network-manager's ifupdown plugin is in managed=true mode.
    - Add a new query interface, 'ifquery', that can be used by upstart
      hooks to ask for the list of possible interfaces that they might need
      to bring up.
    - debian/ifupdown.network-interface.upstart: Replace the init scripts
      with a per-interface Upstart job.
    - debian/ifupdown.networking.upstart: Add a "networking" job that
      partially replaces the networking init script from netbase.
    - debian/control: Bump build-dependency on debhelper for Upstart-aware
      dh_installinit.
    - debian/rules: Due to debhelper always adding /etc/init.d symlinks, we
      must manually remove /etc/init.d/networking for as long as netbase
      still provides it.
    - Add if-up and if-down scripts to emit Upstart events when interfaces
      come up and go down.
    - debian/ifupdown.network-interface-security.upstart: Ensure apport is
      started before interfaces are brought up by either ifupdown or
      network-manager.
    - debian/postinst: If the loopback interface is missing from the config
      in /etc/network/interfaces, add it on upgrade.
    - debian/ifupdown.preinst: Since files in /etc were not conffiles in
      lucid, and /etc/network/if-up.d/upstart and
      /etc/init/network-interface.conf changed between lucid final and
      maverick, add extra handling to avoid spurious conffile prompts.
    - invoke dhclient3 with '-1', meaning it should exit failure if it does
      not receive a response in 60 seconds. (LP: #838968)
    - contrib/ifstate-check: Use /run/ntework/ifstate instead of
      /etc/network/run/ifstate
    - ifup.8: Update man page to indicate that Ubuntu uses /run
      and that it's always writable as it's a temporary filesystem
  * ifupdown.nw: When calling dhclient3, also use /var/lib/dhcp as
    dhclient3 is now a symlink to dhclient and /var/lib/dhcp3 no longer
    exists. (LP: #900234)
  * Mark ifupdown as Multi-Arch foreign
  * Replace remaining references to /var/run/network by /run/network
    (LP: #885506)

ifupdown (0.7~beta2) experimental; urgency=low

  * Put interfaces down in the reverse order than they were
    brought up (Closes: #477650).
  * Fix postinst issues with loopback interface naming
    (Closes: #572396, #545250).
  * Remove old .dpkg-old symlink (Closes: #639612).
  * Document some details on processing /etc/network/if-*.d directories.
  * Terminate ifup if it's still running when doing ifdown.
  * Finally migrate to /run/network.
  * Use FHS names for wvdial pid files (Closes: #255222).
  * Stop on run-parts failure (Closes: #547587).
  * Execute scripts before interface options on *-down (Closes: #346459).
  * Display missing variable name in the error message; make it also a bit
    less obscure (Closes: #502630).
  * Fix wvdial options description (Closes: #534181).
  * Specify interface label (Closes: #645813).
  * Add address scope option for static IPv4 and IPv6 setups.
  * Use FreeBSD version of route, thanks to Robert Millan (Closes: #646291).

ifupdown (0.7~beta1) experimental; urgency=low

  * Update the examples (Closes: #630551).
  * Remove Default-Stop from the LSB headers (Closes: #630506).
  * Add IPv4LL method (Closes: #204641).
  * Add initial DHCPv6 support.
  * Suggest isc-dhcp-client instead of dhcp3-client (Closes: #631414).
  * Support per-architecture build-time rule definitions.
  * Add a syntax (%iface/a/b%) to perform character replacement over
    variable values.
  * Accept VLAN interface names (Closes: #632902).
  * Update test cases.
  * Correct the spelling of the maintainer's last name.
  * Add partial kFreeBSD support (Closes: #630512).
  * Drop 'ifupdown-clean' init script (not needed any more with /run).
 -- Stephane Graber <stgraber at ubuntu.com>   Thu, 12 Jan 2012 10:25:30 +0100

** Changed in: ifupdown (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  alias network interfaces sometimes dont start on boot

Status in ifupdown:
  New
Status in “ifupdown” package in Ubuntu:
  Fix Released
Status in “ifupdown” package in Debian:
  Fix Released

Bug description:
  Binary package hint: upstart

  Hello,
  I have 4 virtual network interfaces configured for autostart on two of my servers. All of them are bound to the same network interface eth0 and have static IP addresses. When I restart the server, sometimes some of them is down after restart and I have to start it manually with ifup. The physical network interface is always up correctly after reboot.
  It does not happen after every reboot and it is not always the same virtual interface which is left down.
  I cannot find any relevant information in syslog regarding this issue. This is a big problem as I have to manually check if all interfaces are running after every restart. 
  I dont know what other info/logfiles should I provide but please feel free to ask.
  Does anyone have similar issue?
  My distro is Ubuntu 10.04.1 Server 64bit.

  Thanx
  Roman Smid

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