upstart event static-network-up emited to early

Bug #1413279 reported by john
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Triaged
High
Unassigned

Bug Description

My understanding of static-network-up is that it should be emited after all devices have successfully come up however it seems like it is been emited too early

stat -c '%n: %z' /run/network/*
/run/network/ifstate: 2015-01-21 01:51:58.301433828 +0000
/run/network/ifup.eth0: 2015-01-21 01:51:58.277433829 +0000
/run/network/ifup.lo: 2015-01-21 01:51:56.749433883 +0000
/run/network/static-network-up-emitted: 2015-01-21 01:51:56.881433878 +0000

As you can see in the above /run/network/ifup.eth0 was updated after /run/network/static-network-up-emitted

I have checked a few systems and this only seems to effect systems with ipv6 configuration.

jbond@lax:~$ lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

jbond@lax:~$ apt-cache policy ifupdown
ifupdown:
  Installed: 0.7.47.2ubuntu4.1
  Candidate: 0.7.47.2ubuntu4.1

jbond@lax:~$ cat /etc/network/interfaces
#addresses changed to rfc3849 and rfc5737
auto lo
iface lo inet loopback

auto eth0

iface eth0 inet static
  address 192.0.2.140/27
  #This is ignored if unbound is installed
  gateway 192.0.2.129
iface eth0 inet6 static
  address 2001:DB8::140/64
  gateway 2001:DB8::1

Tags: ipv6
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Thanks for the bug report john!

This makes perfect sense to me. The original was written assuming eth0 would only have one /e/n/i section, but in the file above, it has two.

I think the answer is to include the address family, so eth0.inet and eth0.inet6 should be two different interfaces so the script will continue to wait until both are up.

Changed in ifupdown (Ubuntu):
status: New → Triaged
importance: Undecided → High
tags: added: ipv6
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.