@Mauricio Faria de Oliveira - with the passwd change in I looked deeper into the proposed libvirt debdiff - Sorry to realize that only now, but please help me to clarify/avoid these issues?
While overall I think it is a great fix to define a known uid/gid I'm not so happy with the fact that it changes the group used for libvirt/qemu on build. I think it needs some more fine tuning to be more usable and less interuptive. Therefore I wanted to discuss the following issues: #1 On a given Xenial install as of today the files are owned by libvirt- qemu:kvm (e.g. pools and images it creates). Those files will still be owned by group "kvm", but after the upgrade libvirt/qemu will fail to access properly right? #2 I see on the xenial diff you remove the groups in postrm. That will leave the files unowned, just with ther numeric gid. Is there any reason to do this delgroup/deluser? And if so why not in Zesty? #3 despite the other changes you left the --ingroup kvm - I think it is right to leave it, but if you go the route of changing it to libvirt- qemu this would need to change as well. Once sorted out Colin might reassign (or a new one :-/) the gid to "kvm" and you could implement it as libvirt-qemu:kvm staying compatible with all setups out there already. My suggestion would be: - stick to libvirt-qemu:kvm - do not drop the user/group on postrm Do you think that would work for you then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637601 Title: UbuntuKVM: migration using NFS mount fails #190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1637601/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
