static-network-up event waits for 'auto' devs without a config stanza

Bug 838968 changed the behavior to block parts of boot waiting for 'auto' network interfaces to come up, by creating a static-network-up upstart event in /etc/network/if-up.d/upstart.

There is a bug in that code, though, were it looked only for 'auto' entries in /etc/network interfaces. If there was a stanza like:
  auto eth0
then this event would wait for eth0 to come up.
This differed from the behavior of 'ifup -a' as 'ifup -a' would not wait for that device unless it also had a configuration.
For example, ifup -a would wait for:
 auto eth0
 iface eth0 inet dhcp
but not for:
 auto eth0

It turns out that it is not uncommon to have 'auto eth0' in an /etc/network/interfaces file without a network.
This was discussed in ubuntu-devel at [1] and then again at [2].

--
[1] http://irclogs.ubuntu.com/2011/09/14/%23ubuntu-devel.html#t00:10
[2] http://irclogs.ubuntu.com/2011/09/14/%23ubuntu-devel.html#t16:38

related bugs:
 bug 850166: ifquery does not respect mappings
 bug 838968: static-network-up event does not wait for interfaces to have an address

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ifupdown 0.7~alpha5.1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Wed Sep 14 13:58:54 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: ifupdown
UpgradeStatus: Upgraded to oneiric on 2010-11-15 (302 days ago)