Create qcow2 images for ubuntu appliances (for LXD and multipass consumption)

[Łukasz Zemczak]

[Impact]

Multipass is moving to LXD for its VM needs so that the company only maintains one QEMU/KVM "wrapper" implementation. To do that without losing the appliance images, the streams need to be compatible with LXD.
For this, we want to start building qcow2 images for all the appliance images alongside of the regular 'raw' images.

[Test Case]

Run a bionic-proposed appliance livefs build (for instance, with SUBARCH=appliance-openhab-core18-amd64), wait for the build to finish and make sure that the list of generated/exported artifacts has a .qcow2 image in it.

[What could go wrong]

As with any shell scripting scenario, if potentially there is a logical bug or a syntax error in the new changes, building regular ubuntu-core images could be broken.

[Brian Murray (brian-murray)]

Hello Łukasz, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.49 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 on 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, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted livecd-rootfs (2.525.49) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+18.04ubuntu1 (i386, amd64, ppc64el, arm64, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Łukasz Zemczak (sil2100)]

Ran a `PROPOSED=1 ARCHES="amd64+appliance-nextcloud-core18-amd64" DIST=bionic CHANNEL=beta for-project ubuntu-appliance cron.daily-live --live` build on ancientminister (so proposed-enabled, beta-channel build of an appliance) and the resulting livefs build generated a .qcow2 image:

https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/ubuntu-core/+build/256893

Via the logs it can be seen that the correct livecd-rootfs version was used: 2.525.49.

Aaaand it also confirmed that the ubuntu-cdimage changes worked, as the qcow2 image has been published to cdimage as well (this link might go away as I might remove the unneeded builds from cdimage):
http://cdimage.ubuntu.com/ubuntu-appliance/18/beta/20210121.2/

...but that's not really part of the verification.

[Launchpad Janitor (janitor)]

This bug was fixed in the package livecd-rootfs - 2.525.49

---------------
livecd-rootfs (2.525.49) bionic; urgency=medium

  * Create additional qcow2 images for ubuntu-appliances (LP: #1906805).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 11 Jan 2021 15:44:20 +0100

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being 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.