[Bug 1882374] Re: Support inclusion of snap from specific track/channel/branch

Éric St-Jean 1882374 at bugs.launchpad.net
Fri Jun 12 15:59:28 UTC 2020


** Changed in: cloud-images
       Status: New => Triaged

-- 
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/1882374

Title:
  Support inclusion of snap from specific track/channel/branch

Status in cloud-images:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in livecd-rootfs source package in Focal:
  New

Bug description:
  We have a bit of a problem right now with LXD in Ubuntu 20.04.

  Users upgrading from 18.04 to 20.04 or those installing LXD through
  the deb shim, will correctly detect that they are on a LTS and auto-
  select a LTS branch of LXD (defaults to 4.0).

  That's however not the case for the images we publish which all
  default to "latest" and so currently pull in LXD 4.1 and soon 4.2.

  
  This isn't good as the behavior we're aiming for is that LTS users should get an LTS track of LXD (4.0) and non-LTS users should get the latest track.

  
  To fix this, we need to be able to specify a track/channel/branch alongside the snap we want to seed and have livecd-rootfs pull that.

  For LXD that would mean "lxd 4.0/stable/ubuntu-20.04" in focal and
  "lxd latest/stable/ubuntu-20.10" on groovy. The exact syntax doesn't
  matter and it's probably fair to assume that the ubuntu branch will
  exist so won't need specifying.

  
  We would like this issue sorted in time for Ubuntu 20.04.1 so we have a good consistent story for those upgrading and those deploying new systems at that time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1882374/+subscriptions



More information about the foundations-bugs mailing list