package libvirt-daemon-system 4.0.0-1ubuntu8.1 failed to install/upgrade: installed libvirt-daemon-system package post-installation script subprocess returned error exit status 1

[David Stafford]

virsh hangs, Virtual Machine Manager hangs on connect to qemu, and upgrade failed.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libvirt-daemon-system 4.0.0-1ubuntu8.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
Date: Sun Jun 10 11:49:32 2018
ErrorMessage: installed libvirt-daemon-system package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-02-12 (482 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=e58ea730-1de6-425d-af8b-fb10f9135add ro rootflags=subvol=@ quiet splash intel_iommu=on pci-stub.ids=intel_iommu=on pci-stub.ids=1462:aaf0,1462:3415,1002:67df,1002:aaf0 vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
SourcePackage: libvirt
Title: package libvirt-daemon-system 4.0.0-1ubuntu8.1 failed to install/upgrade: installed libvirt-daemon-system package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-08 (33 days ago)
mtime.conffile..etc.libvirt.nwfilter.allow-arp.xml: 2017-02-12T23:40:50.917582
mtime.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: 2017-02-12T23:40:51.025579
mtime.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: 2017-02-12T23:40:51.093578
mtime.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: 2017-02-12T23:40:51.237574
mtime.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: 2017-02-12T23:40:51.301573
mtime.conffile..etc.libvirt.nwfilter.clean-traffic.xml: 2017-02-12T23:40:51.417570
mtime.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: 2017-02-12T23:40:51.481568
mtime.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: 2017-02-12T23:40:51.617565
mtime.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: 2017-02-12T23:40:51.665564
mtime.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: 2017-02-12T23:40:51.813560
mtime.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: 2017-02-12T23:40:51.837559
mtime.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: 2017-02-12T23:40:51.893558
mtime.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: 2017-02-12T23:40:51.917557
mtime.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: 2017-02-12T23:40:51.929557
mtime.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: 2017-02-12T23:40:51.937557
mtime.conffile..etc.libvirt.nwfilter.qemu-announce-self-rarp.xml: 2017-02-12T23:40:51.949557
mtime.conffile..etc.libvirt.nwfilter.qemu-announce-self.xml: 2017-02-12T23:40:51.961556
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2017-02-12T23:40:49.461618

[Christian Ehrhardt  (paelzer)]

Hi,
the logs don't indicate a lot, I can only see that it failed to restart service libvirtd.
In general if a service fails to start as-is due to any bug/configuration change then an upgrade will fail as it has to restart the service.

The block of virsh/virt-manager just seem like libvirtd being down, witch matches your fail to restart it.

You'd have to check a few thing on your installation independent to the upgrade to ensure it is running fine which usually is then unblocking the upgrade.
1. does a "systemctl restart libvirtd" work (repetively)
2. if it does get more data on why
  2a. what does "journalctl -xef" while doing so report
  2b. consider enabling libvirtd debugging [1] and check the log
3. try to config your system so that libvirt restarts reliably
4. then re-kick the update of the package

[1]: https://libvirt.org/logging.html

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]