22.04 LTS "sudo do-release-upgrade" does not work

Question

sudo do-release-upgrade -cd

returns

Checking for a new Ubuntu release
New release '22.04' available.
Run 'do-release-upgrade' to upgrade to it.

Then

sudo do-release-upgrade

returns

Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release
set Prompt=normal in /etc/update-manager/release-upgrades.

I think the bug is:

22.04 is not marked as LTS. So do-release-upgrade does not work for the upgrade from 20.04 LTS to 22.04 LTS.

Any workaround except set Prompt=normal in /etc/update-manager/release-upgrades.?

Solution

In case you're coming from 21.10: The Jammy Jellyfish Release Notes (from 2022-04-21) contain a note on Upgrading from Ubuntu 21.10:

Upgrades to 22.04 LTS are currently not enabled (due a bug with snapd and update-notifier) but will be in the next couple of days

In case you're coming from 20.04 LTS: Ubuntu 20.04 will not detect a newer version until Ubuntu 22.04.1 is released, which is scheduled for 2022-08-04.

From Ubuntu Server Upgrading:

Upgrades from one LTS to the next LTS release are only available after the first point release. For example, Ubuntu 18.04 LTS will only upgrade to Ubuntu 20.04 LTS after the 20.04.1 point release. If users wish to update before the point release (e.g. on a subset of machines to evaluate the LTS upgrade) users can force the upgrade via the -d flag.

Comments

[Admin]

There is no bug as that is expected behavior. The upgrade path from 20.04 to 22.04 does not open until after the release of Ubuntu 22.04.1 LTS which is still ~three months into the future. It's the same as prior LTS releases & upgrades (and exactly as documentation states).

[Admin]

If you check back on prior release-upgrade cycle; Canonical/Ubuntu have provided blogs on how to upgrade without waiting... but you'll note the date of when blog is posted varies (ie. 16.04->18.04 was a different time frame to 18.04->20.04) as the Ubuntu Release Team provide input on the blog's release, and it only occurs after they deem it has a good chance of success (full success is when they open the path). If you watched the release; whilst it went rather smoothly; there are still known/issues, the earliest should be fixed Monday (via upgrades), others will likely take longer

[Admin]

Linking back to the documentation stating this would be helpful @guiverc - I didn't know this!

[Admin]

@toonarmycaptain I wasn't thinking of a single wiki/help/blog post at ubuntu.com; but it's found in many places... The release announcement for Ubuntu 22.04 LTS actually state "Users of Ubuntu 21.10 will soon be offered an automatic upgrade to 22.04. Users of 20.04 LTS will be offered the automatic upgrade when 22.04.1 LTS is released, which is scheduled for the 4th of August. For further information about upgrading, see:"..

[Admin]

@toonarmycaptain I'm on the Ubuntu News team (since 2015) thus see most posts for UWN purposes, then tend to forget them, though tend to recall details even if not URLs; but a search engine would be required by me too for much of that now, so I'll suggest you try. I picked on example I used and found ubuntu.com/blog/… for the 18.04->20.04 blog but they'll all be there.. though help/wiki pages on upgrade are often paragraphs on pages about other things release related. I'll suggest using site:*.ubuntu.com in searches

[Admin]

@guiverc fair enough :) I hope I didn't come across harshly; I really would have expected something like this to be be documented if it's SOP (outside of blog posts! Maybe the release cycle page could note this. Thanks for your work :)

[Admin]

I can understand your answer, thank you. But why? It is confusing. What is the difference between xx.04 and xx.04.1?

[Admin]

I think the decision is about stability. Users who run an LTS release often don't need bleeding edge features but prefer stable operation. Whenever a new major version of a software is released, there's a chance of breaking something. The first bugfix release xx.04.1 contains fixes for problems in xx.04, e.g. bugs that occured after upgrading to xx.04 (using -d). These bugs can be found and fixed until xx.04.01, so there's a higher chance for a stable update.