[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy

[Mikolaj Buchwald]

Great news, thank you for the work on this issue!

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

Title:
  No longer possible to use do-release-upgrade on Groovy

Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Released

Bug description:
  Impact
  ------
  It is not possible for users still running Ubuntu 20.10, an end of life release, to upgrade to a supported release of Ubuntu.

  Test Plan
  ---------
  G to I Test
  -----------
  On an Ubuntu 20.10 run `do-release-upgrade` and observe an error message about "an upgrade from Groovy to Impish is not supported".

  With the version of ubuntu-release-upgrader from -proposed (accessible
  by running `do-release-upgrade -p`) the upgrade will be supported and
  complete successfully.

  G to J Test
  -----------
  On an Ubuntu 20.10 system run `do-release-upgrade -d` and observe an error message about "an upgrade from Groovy to Jammy is not supported".

  Now download the tarball from
  http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-
  upgrader-all/current/ and extract it to a subdirectory in /tmp/ and
  execute `jammy`. The upgrade should now proceed and you should not
  encounter any errors upgrading to Ubuntu 22.04 LTS.

  H to J Test
  -----------
  Same as the above but replace Groovy with Hirsute.

  Regression Potential
  --------------------
  Its possible that the upgrade process could fail and users will be left with a broken system instead of an insecure one. However, we'll utilize our automated upgrade testing of Ubuntu desktop (and flavors) to ensure the process works.

  Additionally, the script utils/demotions.py was updated to support falling back from archive.u.c to old-releases.u.c in the event the Release file is not found at the former. Given that pre-build.sh generates the demotions file for impish and the demoted.cfg.impish file was not updated I think there is no chance of regression. in this part of the update.
  SRU Note
  --------
  This'll also need fixing in Jammy so people still running Groovy could upgrade to it when Impish reaches its EoL, however that isn't really testable yet so will be fixed in Jammy later.

  Original Description
  --------------------
  I tried running `do-release-upgrade` on an Ubuntu 20.10 (Groovy Gorilla) system and received an error message from dist-upgrader tarball that an upgrade from Groovy to Impish is not supported. This is because DistUpgrade.cfg (distributed by the tarball) contains `From=Hirsute` and `To=Impish`.

  A minimal fix for this would be to create a DistUpgrade.cfg.groovy and
  ensure `From=Groovy`. You'd want to look at the contents of
  DistUpgrade.cfg and DistUpgrade.cfg.focal to sort out what
  DistUpgrade.cfg.groovy should contain. We might also want to create a
  new demoted.cfg file but the demoted.cfg.focal file might capture
  everything that was demoted. (For what its worth I tested an upgrade
  of a stock Ubuntu 20.10 system to Ubuntu 21.10 by copying
  DistUpgrade.cfg.focal to DistUpgrade.cfg.groovy and did not run into
  any issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions