[Bug 2075969] Re: add support to do-release-upgrade for (EOL) kinetic/lunar to noble upgrades

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:25.04.6

---------------
ubuntu-release-upgrader (1:25.04.6) plucky; urgency=medium

  * all: replace remaining uses of lsb_release
  * DistUpgrade: define From= as list of supported upgrade paths (LP: #2075969)
  * DistUpgradeCache: remove remaining aufs logic
  * DistUpgradeApport: fix call to apport_excepthook (LP: #2096824)
  * Run pre-build.sh: updating mirrors and translations.

 -- Nick Rosbrook <enr0n at ubuntu.com>  Thu, 06 Feb 2025 15:38:50 -0500

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  add support to do-release-upgrade for (EOL) kinetic/lunar to noble
  upgrades

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Noble:
  In Progress

Bug description:
  [Impact]

  Users stuck in kinetic, lunar, and mantic cannot upgrade to noble.

  [Test Plan]

  1. Perform an upgrade from kinetic

  * First, create a jammy container and then manually upgrade it to
  kinetic:

  $ lxc launch ubuntu:jammy j
  $ lxc exec j bash
  $ sed -i 's/archive.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
  $ sed -i 's/jammy/kinetic/g' /etc/apt/sources.list
  $ apt update && apt dist-upgrade -y

  [...]

  * Now, try to upgrade:

  $ do-release-upgrade

  * This will fail with a message along the lines of "upgrades from
  kinetic to noble are not supported." Try with the version in
  -proposed, and it should work now:

  $ do-release-upgrade --proposed

  * This should run to completion.

  2. Do a jammy -> noble upgrade to ensure no adverse side effects were
  introduced:

  $ lxc launch ubuntu:jammy j
  $ lxc exec j bash
  $ do-release-upgrade --proposed

  [Where problems could occur]

  This patch changes the way From= is used in DistUpgrade.cfg. It now
  treats that field as a list and interprets it as allowable upgrade
  paths, instead of requiring a DistUpgrade.cfg.$series to exist for the
  current series.

  This of course could disrupt existing upgrade paths, which is why the
  test plan requires a jammy->noble upgrade, too.

  There were also other places in the code that used that From= field.
  These have been updated, but if any spots were missed, that could
  break existing logic.

  [Original Description]

  [Current Behavior]
  Users still on Kinetic and Lunar are prompted to upgrade to Noble via the motd, however d-r-u claims that upgrading from those releases -> noble is unsupported. You also can not upgrade to mantic anymore, so you would need to manually change your sources to facilitate the upgrade.

  [Expected Behavior]
  Despite these releases being EOL, historically we have allowed d-r-u (hirsute->jammy for example).

  [Replication Steps]
  Launch a lunar instance, upgrade to latest packages, and call do-release upgrade

  [Root Cause]
  It appears that we're missing DistUpgrade.cfg.jammy for kinetic/lunar's UpgradeTools . Ideally we should fix this to allow easier upgrades to supported releases, as we had previously.

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