touch-packages team mailing list archive

[Launchpad Bug Tracker <1442828@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package ifupdown - 0.7.48.1ubuntu9

---------------
ifupdown (0.7.48.1ubuntu9) vivid; urgency=medium

  * debian/ifupdown.ifup-wait-all-auto.service: Wait until ifup's are actually
    done (their pid files go away), not just until ifstate claims that they
    are up (which happens at the beginning of ifup, not at the end). Fixes
    network-online.target to wait until "auto" interfaces are really up.
    (LP: #1442828)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Sun, 12 Apr 2015 06:49:10 -0500

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1442828

Title:
  ifup-wait-all-auto does not wait for interfaces to be fully up

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Vivid:
  Fix Released

Bug description:
  
  The change to ifup@.service done as part of LP 1425376 appears to break the ordering of units marked as "After=network-online.target".  In my specific case, a new service script with "After=network-online.target" is erroneously run concurrently with dhclient.  As the new script depends on networking configuration being complete, it fails as the IP addresses and routes from DHCP are not configured.  This functioned correctly on vivid daily images from a few days ago, and appears to break starting with the vivid daily from approximately 0409.

  Infinity suggested this change as a likely suspect:

  diff -Nru systemd-219/debian/extra/units/ifup@.service systemd-219/debian/extra/units/ifup@.service
  --- systemd-219/debian/extra/units/ifup@.service	2015-04-02 08:08:56.000000000 +0000
  +++ systemd-219/debian/extra/units/ifup@.service	2015-04-07 14:38:38.000000000 +0000
  @@ -6,10 +6,8 @@
   DefaultDependencies=no
   
   [Service]
  -Type=oneshot
  -ExecStart=/sbin/ifup --allow=hotplug %I
  -ExecStartPost=/sbin/ifup --allow=auto %I
   # only fail if ifupdown knows about the iface AND it's not up
  -ExecStartPost=/bin/sh -c 'if ifquery %I >/dev/null; then ifquery --state %I >/dev/null; fi'
  +ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \
  +    if ifquery %I >/dev/null; then ifquery --state %I >/dev/null; fi'
   ExecStop=/sbin/ifdown %I
   RemainAfterExit=true

  and, indeed, reverting this (copying ifup@.service from a few-days old
  vivid image to a current image) resolves the problem.

  The affected version is  ubuntu-vivid-daily-amd64-server-20150409.2
  (installed via AWS).

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