/etc/network/if-up.d/upstart emits static-network-up too early
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Triaged
|
High
|
Unassigned |
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/
The result is that things that were waiting on 'static-
(note also that this happens to cause strange behavior in bug 1352255).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ifupdown 0.7.47.2ubuntu4.1
ProcVersionSign
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)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago)
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 |
Nice find, and confirmed on trusty.