snap seed with channel breaks ubuntu-cpc:minimized builds on focal

[Robert C Jennings]

[Impact]

 * Focal ubuntu-cpc:minimized builds fail (see Original Description)

[Test Case]

 * build ubuntu-cpc:minimized
   * autopkgtest will catch this now, but didn't previously because the seed had yet to change

[Regression Potential]

 * This is a very low risk change that is only in the code path ubuntu-cpc:minimized and the regression would require us to add a seeded snap that had a lxd=something that wasn't lxd, however the snap store doesn't allow '=' in name, so I think we're good.

[Other Info]

 * None

[Original Description]

The seed now specifies the lxd snap in focal as
'lxd=4.0/stable/ubuntu-20.04' which doesn't match the expectations of
the code with looks for lxd as the only snap in the seed for minimized
images. This patch updates the pattern to accept 'lxd' or 'lxd=*'.

The failure we see in the build is:

W: No seed matching task cloud-image
snap: considering required
snap: considering minimal
snap: considering standard
snap: considering server
snap: found lxd=4.0/stable/ubuntu-20.04
Unexpected seeded snap for ubuntu-cpc:minimized build: lxd=4.0/stable/ubuntu-20.04
Build failed

[Launchpad Janitor (janitor)]

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

---------------
livecd-rootfs (2.679) groovy; urgency=medium

  * Handle seeded lxd snap with channel name for ubuntu-cpc:minimized
     (LP: #1889470)

 -- Robert C Jennings <email address hidden> Wed, 29 Jul 2020 14:55:57 -0500

[Timo Aaltonen (tjaalton)]

Hello Robert, or anyone else affected,

Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.664.5 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[David Krauser (davidkrauser)]

Autopkgtests for v2.664.5 have passed (which build ubuntu-cpc:minimized).

[Launchpad Janitor (janitor)]

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

---------------
livecd-rootfs (2.664.5) focal; urgency=medium

  [ Robert C Jennings ]
  * Handle seeded lxd snap with channel name for ubuntu-cpc:minimized
    (LP: #1889470)

  [ Cody Shepherd ]
  * Add dist-upgrade to bootable-buildd hook to ensure the built image
    doesn't contain vulnerable kernels or other packages. LP: #1891061.
  * Don't explicitly install grub-efi-amd64-signed, it's a dependency of
    shim-signed.

 -- Steve Langasek <email address hidden> Tue, 04 Aug 2020 12:39:27 -0700

[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.

[Christian Ehrhardt  (paelzer)]

This was blocking debootstrap and qemu.
No tests were in the autopkgtest queue for either since this was released, running against the former 2.664.4 they failed. I have retriggered all of them.
Thanks for the fix!