Ubuntu
libvirt package

[jaunty] upgrade to 0.6.0 leaves a non-working libvirtd

Bug #328093 reported by Chris Jones
6
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Intrepid and later versions of libvirtd run as the group "libvirtd".
The 0.6.0 upload in jaunty wants to run as "libvirt", but does not do any transition work in pre/postinst.

The resulting behavious is that the libvirtd init script claims success in starting the daemon, but actually syslog shows that it exits almost immediately when it is unable to find its group.

Revision history for this message
Chris Jones (cmsj) wrote :

Confirming as we've seen this on two machines

Changed in libvirt:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 0.6.0-1ubuntu2

---------------
libvirt (0.6.0-1ubuntu2) jaunty; urgency=low

  * Accidentally dropped our changes to
    0003-allow-libvirt-group-to-access-the-socket.patch, causing the
    group as which libvirtd expected to run to be wrong. Change it back
    to "libvirtd" rather than "libvirt". (LP: #328093)

 -- Soren Hansen <email address hidden> Wed, 11 Feb 2009 16:10:28 +0100

Changed in libvirt:
status: Confirmed → 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.