Ubuntu
libvirt package

libvirt-bin upstart job will not be started again on transition from runlevel 1 to 2

Bug #820675 reported by Clint Byrum
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

This start on:

start on (runlevel [2345] and stopped networking RESULT=ok)

Will not be satisfied when the raw transition of runlevel 1 to 2 is done, but the stop on will have stopped libvirt-bin.

Tags: runlevel1
Ursula Junque (ursinha)
Changed in libvirt (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hi Clint,

is this still a concern?

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

Looks like it was fixed, thanks Serge!

libvirt (0.9.8-2ubuntu9) precise; urgency=low

  [ Stefan Bader ]
  * xen_hypervisor: libvirtd can be started before xenfs has been loaded
    as a module. A missing privcmd file is not necessarily a permanent
    error. (LP: #922486)

  [ Serge Hallyn ]
  * debian/libvirt-bin.upstart: start on just 'runlevel [2345]'

 -- Serge Hallyn <email address hidden> Wed, 08 Feb 2012 11:20:35 -0600

Changed in libvirt (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.