Hi Nur,
that is odd the handling is as following.

In the past there was a group libvirtd - new packaging in Debian and
Ubuntu renamed that to libvirt but the install handles that.

In case of a new install you would have those groups for libvirt:
libvirt:x:132:paelzer                                                           
 
libvirt-qemu:x:64055:libvirt-qemu 

But if you are on an upgrade form an older version to properly work with old 
filed created under the old user you'd get:
libvirtd:x:132:paelzer                                                          
 
libvirt:x:132:paelzer                                                           
 
libvirt-qemu:x:64055:libvirt-qemu 

The GID is the same, and therefore both names are essentially the same
group.

The snippet for that is in libvirt-daemon-system.postinst and I don't see yet 
how that would "remove" the libvirtd group.
     if ! getent group libvirt >/dev/null; then
        if getent group libvirtd >/dev/null; then
            gid=`getent group libvirtd | getent group libvirtd  | cut -d: -f3`
            groupadd --system --non-unique --gid "$gid" libvirt
        else
            addgroup --quiet --system libvirt
        fi
     fi

This is this way since yakkety (16.10) and so far was not an issue.

So the behavior should be:
- new installs since >=Yakkety, you have just group "libvirt"
- upgrade <=Xenial have libvirtd, and you get libvirtd AND libvirt on the same 
GID

Nur, could you please outline:
- what exact the error was that made your system need the libvirtd group?
- a scenario how you'd ever have had a libvirtd group given that you Started 
with 17.04 after the changes I referred to?

If this is a 3rd party automation/script you'd have to adapt to the new
group name for new installs. As mentioned upgrades will be handled - but
all of this is true since >=16.10.

Waiting for your reply ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769251

Title:
  libvirtd group not automatically created when libvirt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1769251/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to