Comment 74 for bug 1637601

------- Comment From <email address hidden> 2017-01-20 08:47 EDT-------
Verification done with Xenial. All good!

# lsb_release -d
Description: Ubuntu 16.04.1 LTS

Previous Package:
----------------

0) No existing user/uid:

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
#

User is created w/ the next available uid

# apt-get install --yes --no-install-recommends libvirt{0,-bin}=1.3.1-1ubuntu10.6

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
#

Proposed Package:
----------------

1) With existing user (e.g., package update)

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

User uid remains the same:

# apt-get install --yes --no-install-recommends libvirt{0,-bin}=1.3.1-1ubuntu10.7

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
#

2) Without existing user (e.g., new install)

# apt-get purge --yes libvirt{0,-bin}
Reading package lists... Done

# userdel libvirt-qemu

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
#

User uid is set to the reserved uid:

# apt-get install --yes --no-install-recommends libvirt{0,-bin}=1.3.1-1ubuntu10.7

# id libvirt-qemu
uid=64055(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
libvirt-qemu:x:64055:117:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false

3) Without existing user (e.g., new install) _but_ with uid taken

# apt-get purge --yes libvirt{0,-bin}

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
uidtaken:x:64055:1001::/home/uidtaken:

# apt-get install --yes --no-install-recommends libvirt{0,-bin}=1.3.1-1ubuntu10.7

User uid is set to the next available uid:

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
uidtaken:x:64055:1001::/home/uidtaken:

------- Comment From <email address hidden> 2017-01-20 08:49 EDT-------
BTW,
*again*, sorry for all the noise/attachments from the bug mirroring.
This problem has already been passed along to its development team.
I have no idea why this happens.