upstart-udev-bridge claims to emit events it does not emit

Bug #819928 reported by Clint Byrum on 2011-08-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Low
Clint Byrum
upstart (Ubuntu)
Low
Clint Byrum

Bug Description

upstart-udev-bridge says

emits *-device-*

But it does not actually emit net-device-up for instance.

It only emits

*-device-added

and

*-device-removed

Changing this to be correct and running initctl check-config reveals that net-device-up is not emitted (should be in the 'networking' and 'network-interface' jobs).

Changed in upstart (Ubuntu):
assignee: nobody → Clint Byrum (clint-fewbar)
importance: Undecided → Low
status: New → In Progress
Changed in ifupdown (Ubuntu):
status: New → In Progress
assignee: nobody → Clint Byrum (clint-fewbar)
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package upstart - 1.3-0ubuntu6

---------------
upstart (1.3-0ubuntu6) oneiric; urgency=low

  [ Steve Langasek ]
  * Fix maintainer field to be compliant with policy definition

  [ Clint Byrum ]
  * conf/rc.conf: document events that are emitted by sysvinit
    jobs to quiet 'initctl check-config'
  * extra/conf/upstart-udev-bridge.conf: narrow definition to
    only the events actually emitted. (LP: #819928)
  * debian/conf/failsafe.conf: new job for critical services to
    start on.
  * conf/rc-sysinit.conf: start after static-network-up or failsafe
    so that runlevel 2 is only entered with all static net interfaces
    up. (LP: #580319)
 -- Clint Byrum <email address hidden> Wed, 10 Aug 2011 08:44:43 -0500

Changed in upstart (Ubuntu):
status: In Progress → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ifupdown - 0.7~alpha5.1ubuntu3

---------------
ifupdown (0.7~alpha5.1ubuntu3) oneiric; urgency=low

  * Document what events are emitted properly. (LP: #819928)
 -- Clint Byrum <email address hidden> Mon, 22 Aug 2011 11:28:32 +0100

Changed in ifupdown (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers