package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1375910 reported by Simon THOBY
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
High
Unassigned
Trusty
Fix Released
High
Unassigned

Bug Description

======================================================
Impact: libvirt package upgrade can fail if user deletes /etc/libvirt/qemu.conf
Test case:
 sudo apt-get install libvirt-bin
 sudo rm /etc/libvirt/qemu.conf
 sudo apt-get install --reinstall libvirt-bin
Regresion potential: none, we only check that the file is present before trying to chown+chmod it.
======================================================

I ran sudo apt-get update && sudo apt-get upgrade
After that, the differents programs installed ans updated but libvirt-bin can't be configure by dpkg cause /etc/libvirt/qemu.conf don't exist.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libvirt-bin 1.2.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Tue Sep 30 12:11:16 2014
DuplicateSignature: package:libvirt-bin:1.2.8-0ubuntu6:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-09-28 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: libvirt
Title: package libvirt-bin 1.2.8-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.qemu.conf: [modified]
mtime.conffile..etc.libvirt.qemu.conf: 2014-09-30T12:11:54.303971

Revision history for this message
Simon THOBY (simonthoby-deactivatedaccount) wrote :
Changed in libvirt (Ubuntu):
assignee: nobody → Simon THOBY (simonthoby)
tags: removed: need-duplicate-check
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for reporting this bug. Was /etc/libvirt/qemu.conf not existing on purpose?

Indeed the libvirt-bin.postinst should allow for that file not existing rather than fail package install.

Changed in libvirt (Ubuntu):
importance: Undecided → High
status: New → In Progress
Changed in libvirt (Ubuntu Precise):
importance: Undecided → High
Changed in libvirt (Ubuntu Trusty):
importance: Undecided → High
description: updated
no longer affects: libvirt (Ubuntu Precise)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.2.8-0ubuntu8

---------------
libvirt (1.2.8-0ubuntu8) utopic; urgency=medium

  * libvirt-bin.postinst: fix syntax error (s/if/fi/)
 -- Serge Hallyn <email address hidden> Tue, 30 Sep 2014 13:07:19 -0500

Changed in libvirt (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Simon, or anyone else affected,

Accepted libvirt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libvirt (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Verified in trusty-proposed.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.6

---------------
libvirt (1.2.2-0ubuntu13.1.6) trusty-proposed; urgency=medium

  * 9029-ovs-delete-port-if-it-exists-when-adding-new-one: cherrypick commit
    33445ce from upstream (LP: #1343262)
  * fix migration failure with ssh password authentication (LP: #1365947)
    - 9030-virsh-add-keepalive-in-new-vshconnect-fn
    - 9031-cmdmigrate-move-vshconnect-before-vshwatchjob
    - 9032-virsh-initialize-vsh-data-in-cmdmigrate
  * libvirt-bin.postinst: check for confiles whichhave been removed rather
    than fail package install (LP: #1375910)
  * Support incoming migration from 12.04 hosts (LP: #1374622)
    - debian/patches/support-incoming-qemu-kvm: add a flag to
      /etc/libvirt/qemu.conf to specify whether pc-1.0 came from a 12.04 host
    - Add a note in README.Debian.
 -- Serge Hallyn <email address hidden> Tue, 30 Sep 2014 13:54:31 -0500

Changed in libvirt (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.