Serge said:
> There could well be a libvirt bug as well, but if postinst fails ungracefully
if libvirt is stopped isn't that a packaging bug in uvtool-libvirt?
I disagree. uvtool-libvirt requires libvirtd to be running, and libvirt-
bin is expected to ship it running. If a user intervenes by
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641801
Title:
package uvtool-libvirt (not installed) failed to install/upgrade:
subprocess installed
Maybe it's related to this problem:
KVM + Xenial Server. libvirt-bin won't configure
http://askubuntu.com/questions/762924/kvm-xenial-server-libvirt-bin-wont-configure#763935
I had to do something similar to get libvirt-bin started again:
$ sudo systemctl stop apparmor.service
$ sudo apt-get
On 2016-11-15 06:52 AM, Serge Hallyn wrote:
> Wait, what? Perhaps he purposely had disabled it on purpose?
I may have done just that, but I can't remember. I was eager to switch
to LXD in Ubuntu 16.04 instead of using LXC and uvtool in Ubuntu 14.04.
I was surprised that it made the upgrade
Quoting Robie Basak (1641...@bugs.launchpad.net):
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> It looks like libvirtd was not running at the time of an upgrade, and
> this caused uvtool-libvirt's postinst to fail. So this is a libvirt bug,
> not a
>From log:
Setting up uvtool-libvirt (0~bzr99-0ubuntu1) ...
2016/11/14 18:40:59 socat[16105] E connect(5, AF=1
"/var/run/libvirt/libvirt-sock", 31): No such file or directory
libvirtd does not appear to be listening on "/var/run/libvirt/libvirt-sock".
On Ubuntu, libvirtd is managed with the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like libvirtd was not running at the time of an upgrade, and
this caused uvtool-libvirt's postinst to fail. So this is a libvirt bug,
not a uvtool bug. Reassigning.
We've seen a few cases of libvirtd
