touch-packages team mailing list archive

[Launchpad Bug Tracker <1442828@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:


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).

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

-- 
change for LP 1425376 breaks systemd After=network-online.target
https://bugs.launchpad.net/bugs/1442828
You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.