Disable "latest" as upgrade option on focal

Bug #1964833 reported by Stéphane Graber
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxd (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

The "lxd" transitional deb-to-snap package currently offers "3.0", "4.0" and "latest" as track options with "4.0" being the recommended and default one.

Starting with LXD 5.0, it will no longer be possible to upgrade from LXD 3.0 without first going through LXD 4.0. As a result, the deb-to-snap logic in focal should be updated to remove "latest" as an option.

Instead users will have to pick between "3.0" or "4.0" and can then upgrade afterwards by switching snap track.

The impact from this should be minimal as most users have already gone through this process and those who haven't are likely to go with the default option anyway (4.0).

[Impact]
LXD 5.0 (to be released end of March) will break the upgrade path when coming from a release prior to 4.0.0.

The deb-to-snap logic in Ubuntu 20.04 currently offers "latest" as a track for users switching to the snap (from 3.0 deb). This option will start breaking once 5.0 is released and should be removed from the upgrader prior to that.

The users will lose the option to go straight to "latest" during the deb-to-snap process instead being pushed towards "4.0" which they can then upgrade from after the fact using "snap refresh".

The "4.0" track was already the default and used by virtually all users to date, so the change is unlikely to be particularly visible.

[Test plan]
Get an Ubuntu 18.04 system, run "lxd init --auto" to initialize LXD, then upgrade to 20.04 and confirm that the debconf prompt defaults to "4.0" and does not offer "latest" as a track option.

[Where problems could occur]
If this SRU isn't in focal-updates by the time LXD 5.0 releases to latest/stable (first week of April), some users may chose "latest" during the upgrade which will fail and fail the LTS-to-LTS process giving them a hard to recover system.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Note that I'm not pushing for an impish version of this change as this package in impish is unused.

The transitional "lxd" package is only relevant when upgrading from a pre-snap system which is only possible when upgrading from bionic to focal. The package has now been removed entirely from jammy, something we should have done a few releases ago.

description: updated
Changed in lxd (Ubuntu):
status: New → Fix Committed
status: Fix Committed → In Progress
Revision history for this message
Stéphane Graber (stgraber) wrote :

lxd_0.10_source.changes uploaded to the queue

Revision history for this message
Chris Halse Rogers (raof) wrote : Proposed package upload rejected

An upload of lxd to focal-proposed has been rejected from the upload queue for the following reason: "Not-entirely-necessary change of translatable string".

Revision history for this message
Chris Halse Rogers (raof) wrote :

An upload of lxd to focal-proposed has been rejected from the upload queue for the following reason: "Oops, sorry.".

Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Stéphane, or anyone else affected,

Accepted lxd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/1:0.10 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 lxd (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed verification-needed-focal
Revision history for this message
Stéphane Graber (stgraber) wrote :

Just tested this by running the new package on an Ubuntu 18.04 system with LXD 3.0 running (including one running instance).

The prompt showed up as expected and indeed just offered 3.0 and 4.0 with 4.0 selected as default.
Upgrade worked and container is still functional on the 4.0 snap.

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxd - 1:0.10

---------------
lxd (1:0.10) focal; urgency=medium

  * Disable the "latest" track as it's no longer a valid upgrade target
    when coming from LXD 3.0. (LP: #1964833)
  * Unmount shmounts/devlxd prior to removal. (LP: #1876979)

 -- Stéphane Graber <email address hidden> Mon, 14 Mar 2022 17:45:36 -0400

Changed in lxd (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Stéphane Graber (stgraber) wrote : Update Released

The verification of the Stable Release Update for lxd 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.

Changed in lxd (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.