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

Łukasz Zemczak 1882374 at bugs.launchpad.net
Thu Jul 23 21:16:22 UTC 2020


Hello Stéphane, 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.4 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.

** Changed in: livecd-rootfs (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
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:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Can only seed snaps from latest track, yet there is desire to
  support "LTS" tracks.

   * Add support for snap:$SNAP=$TRACK/$RISK/$BRANCH syntax in seeds,
  e.g.

  ```
  * snap:lxd=4.0/stable/ubuntu-20.10
  ```

  [Test Case]

   * Use full-channel specification in the seed and test build ubuntu-
  server, subproject live build.

  [Regression Potential]

   * Backwards compatible with existing seeds.
   * New code only used when full channel is specified in the seed.

  [Other Info]
   
   * Original bug report

  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