documentation flaw "libvirt", rather than "libvirtd" group

Bug #1095140 reported by caludo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
High
Serge Hallyn
Precise
Fix Released
High
Serge Hallyn
Quantal
Won't Fix
High
Unassigned

Bug Description

The documentation in /usr/share/doc/libvirt-bin/README.Debian.gz talks about access control and refers to a group called "libvirt". Apparently, this group is actually called "libvirtd" on Ubuntu.

Quote:

> Note that *every* user on the system has access to xend then. Better use
> libvirtd to access xen with unprivileged users and add the users to the
> "libvirt" group (see "Access Control" below).

> Access Control
> ==============
> Access to the libvirt socket is controlled by membership in the "libvirt" group.
> If you want to manage VMs as non root you need to add a user to that group.

I'm using Ubuntu 12.10, libvirt-bin version 0.9.13-0ubuntu12.1.

====================================
SRU Justification:
1. Impact: README.Debian tells admins to place users who want to use libvirt into the wrong group.
2. Development fix: update documentation
3. Stable fix: same as development fix
4. Test case: look at /usr/share/doc/libvirt-bin/README.Debian.gz and look for
"libvirtd" group
in stead of
"libvirt" group"
5. Regression potential: this is only a documentation update.
====================================

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for submitting this bug. Valid in 13.04 as well.

Changed in libvirt (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in libvirt (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
Changed in libvirt (Ubuntu Precise):
status: New → Confirmed
Changed in libvirt (Ubuntu Quantal):
status: New → Confirmed
importance: Undecided → High
Changed in libvirt (Ubuntu Precise):
importance: Undecided → High
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

(I will SRU this for precise and quantal after the next precise release in a few days)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.0.2-0ubuntu4

---------------
libvirt (1.0.2-0ubuntu4) raring; urgency=low

  * Update Readme.Debian
    - we use libvirtd, not libvirt group (LP: #1095140)
    - we add users from sudo, not admin group, to libvirtd.
  * libvirt-bin.postinst: put users from sudo, not admin group, into group
    libvirtd. (LP: #1124127)
 -- Serge Hallyn <email address hidden> Wed, 13 Feb 2013 09:47:58 -0600

Changed in libvirt (Ubuntu):
status: Triaged → Fix Released
Changed in libvirt (Ubuntu Precise):
assignee: nobody → Serge Hallyn (serge-hallyn)
status: Confirmed → In Progress
description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello caludo, or anyone else affected,

Accepted libvirt into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libvirt/0.9.8-2ubuntu17.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libvirt (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

verified in precise-proposed.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.8

---------------
libvirt (0.9.8-2ubuntu17.8) precise-proposed; urgency=low

  [ Adam Conrad ]
  * libvirt-bin.postinst: also put admin group members into the libvirtd
    group, to support systems installed before precise. (LP: #1124127)
  * libvirt-bin.postinst: use getent group instead of grep /etc/group

  [ Serge Hallyn ]
  * Update README.Debian:
    - we use libvirtd, not libvirt group (LP: #1095140)
    - we add users from sudo, not admin group, to libvirtd.
  * Handle two usb devices with same vendor/id (LP: #1082213)
    - ubuntu/qemu-Keep-list-of-USB-devices-attached-to-domains
    - ubuntu/usb-create-functions-to-search-usb-device
    - ubuntu/qemu-call-usb-search-function-for-hostdev

  [ Andres Lagar-Cavilla ]
  * Add RESUME event listener to qemu monitor (LP: #1097824)
    - ubuntu/handle_resume.patch

  [ Kirill Zaborsky ]
  * Add proper handling for EINTR signal (LP: #1092826)
    - ubuntu/fix-poll.patch
 -- Serge Hallyn <email address hidden> Thu, 21 Feb 2013 08:38:35 -0600

Changed in libvirt (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in libvirt (Ubuntu Quantal):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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