/etc/network/if-up.d/upstart emits static-network-up too early

Bug #1379427 reported by Scott Moser on 2014-10-09
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)

Bug Description

I came across this when debugging bug 1352255.
as implemented right now (trusty and utopic) the 'static-network-up' event is emitted when each 'auto' interface has had *an* address configured, as opposed to *all* addresses configured.

Heres why:
 ifupdown calls runparts on /etc/network/if-up.d/ after each stanza for a network inteface, rather than once after *all* stanzas are executed.

The result is that things that were waiting on 'static-network-up', expecting that would provide them with expected networking are not actually guaranteed anything other than the first stanza for each interface.

(note also that this happens to cause strange behavior in bug 1352255).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ifupdown
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu Oct 9 12:37:10 2014
InstallationDate: Installed on 2011-12-06 (1037 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
 PATH=(custom, no user)
SourcePackage: ifupdown
UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago)

Scott Moser (smoser) wrote :
Clint Byrum (clint-fewbar) wrote :

Nice find, and confirmed on trusty.

Changed in ifupdown (Ubuntu):
status: New → Triaged
importance: Undecided → High
summary: - /etc/network/if-up.d/upstart emits static-network-up to early
+ /etc/network/if-up.d/upstart emits static-network-up too early
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers