Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails

[William Kelly]

=====================
SRU Justification
1. Impact: cloud archive users cannot upgrade cleanly
2. Development fix: properly mark qemu-utils as replacing qemu-kvm to force conflicting files to be replaced.
3. Stable fix: same as development fix
4. Test case: see below. (basically, install grizzly cloud archive on precise; then upgrade to havana)
5. Regression potential: we are only marking qemu-utils as conflict/replacing old qemu-kvm, so there should be no regressions.
=======================

When upgrading from the grizzly qemu packages to the havana packages (1.0+noroms-0ubuntu14.11 to 1.5.0+dfsg-3ubuntu5~cloud0), initial package configuration fails:

Preparing to replace qemu-utils 1.0+noroms-0ubuntu14.11 (using .../qemu-utils_1.5.0+dfsg-3ubuntu5~cloud0_amd64.deb) ...
Unpacking replacement qemu-utils ...
dpkg: error processing /var/cache/apt/archives/qemu-utils_1.5.0+dfsg-3ubuntu5~cloud0_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/qemu-io', which is also in package qemu-kvm 1.0+noroms-0ubuntu14.11
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package qemu-system-common.
dpkg: considering deconfiguration of qemu-utils, which would be broken by installation of qemu-system-common ...
dpkg: yes, will deconfigure qemu-utils (broken by qemu-system-common).
Unpacking qemu-system-common (from .../qemu-system-common_1.5.0+dfsg-3ubuntu5~cloud0_amd64.deb) ...
De-configuring qemu-utils ...
dpkg: error processing /var/cache/apt/archives/qemu-system-common_1.5.0+dfsg-3ubuntu5~cloud0_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/qemu.1.gz', which is also in package qemu-kvm 1.0+noroms-0ubuntu14.11

apt-get install -f will finish the installation.

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug.

In raring, qemu-utils had Replaces: qemu-kvm. In saucy it doesn't any more.
If you upgrade using do-release-upgrade a step at a time, you don't see
this error. However, this will break LTS-to-LTS upgrades to trusty when
it is released.

qemu-utils must continue to have

Breaks: qemu-user (<< 0.11.1-2), qemu-kvm (<< 1.2.0.dfsg-1)
Replaces: qemu-user (<< 0.11.1-2), qemu-kvm (<< 1.2.0.dfsg-1)

 status: confirmed
 priority: high

[William Kelly (the-william-kelly)]

Hello Serge,

I am sorry! I put this bug in on the saucy package, because I believe it is what the cloud archive repository is using to provide openstack packages for precise. I should have been more clear, and I apologize if this bug is filed against the wrong project -- the packaging situation for cloud archive confuses me.

In any case, I am using the openstack grizzly precise release in cloud archive, testing upgrades to the havana precise release in cloud archive.

The issue is easily reproduced by installing qemu from grizzly cloud archive, adding a havana source, and performing apt-get upgrade.

Is this the right place to report this bug?

[Serge Hallyn (serge-hallyn)]

Hi,

If this only affected the cloud archive updates then the bug would
probably belong against the cloud archive itself (if that exists
as a project), since normally you must update from p to q to r to
s, which works fine. However it IS valid against the ubuntu qemu packages
because, once trusty is released, LTS-to-LTS updates from precise to
trusty would break.

I've just pushed the fix to trusty. I think it's SRU-able to saucy
because fixing it with a delta in the cloud archive would be more
maintenance work later as more bugs get SRUd.

[William Kelly (the-william-kelly)]

Thanks, Serge!

[Launchpad Janitor (janitor)]

This bug was fixed in the package qemu - 1.6.0+dfsg-2ubuntu2

---------------
qemu (1.6.0+dfsg-2ubuntu2) trusty; urgency=low

  * debian/control: qemu-utils must Replace: qemu-kvm as it did in raring,
    to prevent lts-to-lts updates from breaking. (LP: #1243403)
 -- Serge Hallyn <email address hidden> Wed, 23 Oct 2013 14:31:05 -0500

[Brian Murray (brian-murray)]

Hello William, or anyone else affected,

Accepted qemu into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu/1.5.0+dfsg-3ubuntu5.1 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!

[Jacob Godin (jacobgodin)]

This bug is also present in Precise when using the Cloud Archive. To workaround, qemu-kvm and qemu-common must be removed via dpkg.

[Serge Hallyn (serge-hallyn)]

@Jacob,

once someone verifies the fix in saucy, and the fix is promoted to saucy-updates, then it will show up in the cloud archive.

(To put it another way - the bug is not in precise; it is in the version in cloud archive, which will be pulled into the cloud archive from saucy when that is updated)

[William Kelly (the-william-kelly)]

Hello Serge,

I am sorry for the slow response on this. I had a chance to test the packages, and it appears that they have been broken by a change to another package: qemu-system-x86 deps on ipxe-qemu, which appears to have been superceded by ipxe.

The packages are uninstallable in proposed.

root@wilk-aio3:~# apt-cache policy qemu-system-x86
qemu-system-x86:
  Installed: (none)
  Candidate: 1.5.0+dfsg-3ubuntu5.1
  Version table:
     1.5.0+dfsg-3ubuntu5.1 0
        700 http://archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 Packages
     1.5.0+dfsg-3ubuntu5 0
        100 /var/lib/dpkg/status

root@wilk-aio3:~# apt-get install qemu-system-x86
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qemu-system-x86 : Depends: ipxe-qemu but it is not installable
E: Unable to correct problems, you have held broken packages.

root@wilk-aio3:~# apt-cache policy ipxe-qemu
ipxe-qemu:
  Installed: (none)
  Candidate: (none)
  Version table:

https://launchpad.net/ubuntu/saucy/amd64/ipxe-qemu

Regards,
Will Kelly

[Serge Hallyn (serge-hallyn)]

> root@wilk-aio3:~# apt-cache policy ipxe-qemu
> ipxe-qemu:
> Installed: (none)
> Candidate: (none)
> Version table:

Can you please show your /etc/apt/sources.list and any files
under /etc/apt/sources.list.d? My saucy box says:

$ apt-cache policy ipxe-qemu
ipxe-qemu:
  Installed: 1.0.0+git-20130710.936134e-0ubuntu1
  Candidate: 1.0.0+git-20130710.936134e-0ubuntu1
  Version table:
 *** 1.0.0+git-20130710.936134e-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

[William Kelly (the-william-kelly)]

Hello!

Unfortunately, I destroyed the vm I was testing on, but there was definitely an issue with my sources or the mirror (kernel.org) I was using, as I was able to successfully upgrade from precise's qemu to saucy's qemu with no issues. I do see ipxe-qemu in the saucy main repo now.

The qemu upgrade issues are resolved.

Regards,
Will Kelly

[Colin Watson (cjwatson)]

The verification of the Stable Release Update for qemu 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 regresssions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package qemu - 1.5.0+dfsg-3ubuntu5.1

---------------
qemu (1.5.0+dfsg-3ubuntu5.1) saucy-proposed; urgency=low

  * debian/control: qemu-utils must Replace: qemu-kvm as it did in raring,
    to prevent lts-to-lts updates from breaking. (LP: #1243403)
 -- Serge Hallyn <email address hidden> Wed, 30 Oct 2013 11:52:44 -0500