[Bug 1891505] Re: LXD appliance image needs to follow the 4.0 track

[Launchpad Bug Tracker]

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

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

  * Apparently the lxd appliance needs to use a custom track (4.0) and since
    model assertions do not accept track names in required-snaps, we need to do
    this by hand during build. (LP: #1891505)

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com>  Wed, 12 Aug
2020 15:58:19 +0200

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1891505

Title:
  LXD appliance image needs to follow the 4.0 track

Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Per definition of the appliance, we need to follow the 4.0 LTS track instead of 'latest', which is default. I originally assumed that the model assertion will be self-contained and has everything that's needed, but it seems that required-snaps for UC18 are not allowed to have custom tracks set (this is only supported for UC20).
  So to make things work, we need to work-around it by adding the custom lxd snap track via livecd-rootfs.

  [Test Case]

  Perform a -proposed enabled ubuntu-appliance cdimage build for the lxd
  appliance and confirm via the manifest that the lxd snap is taken from
  the right track.

  [Regression Potential]

  If anything, all possible regressions are in ubuntu-core image builds,
  like invalid extra snaps could be installed or the builds could start
  failing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1891505/+subscriptions