not possible to upgrade from Xenial and jump over an unsupported release

Bug #1692092 reported by Brian Murray on 2017-05-19
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
High
Brian Murray
Zesty
High
Brian Murray

Bug Description

With the changes to update-manager in bug 1497024 it should be possible to upgrade from Ubuntu 16.04 to 17.04 (provided 16.10 is End of Life). While update-manager will download the zesty.tar.gz file it will not run and will instead say "An upgrade from 'X' to 'Z' is not supported with this tool." This is because ubuntu-release-upgrader has not been configured to upgrade from 16.04 to 17.04.

[Test Case]
1) Run do-release-upgrade (notice it download yakkety.tar.gz)
2) Set yakkety to unsupported in ~/.cache/update-manager-core/meta-release
3) Run do-release-upgrade again (notice it download zesty.tar.gz)

With the dist-upgrader tarball currently available you'll receive an error message about the upgrade path being unsupported. With the version of the dist-upgrader tarball in proposed (accessible by running do-release-upgrade -p and modifying meta-release-proposed in the cache folder) you will not receive that error message.

[Regression Potential]
It's possible the upgrade won't work for people, but I'll be watching out for issues and its better than we resolve upgrade issues now rather then when people are upgrading from LTS to LTS.

Related branches

tags: added: artful dist-upgrade zesty
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu Zesty):
importance: Undecided → High
assignee: nobody → Brian Murray (brian-murray)
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → In Progress
Changed in ubuntu-release-upgrader (Ubuntu Zesty):
status: New → In Progress
description: updated
summary: - not possible to upgrade from Xenial to Zesty
+ not possible to upgrade from Xenial past and unsupported release
summary: - not possible to upgrade from Xenial past and unsupported release
+ not possible to upgrade from Xenial past an unsupported release
summary: - not possible to upgrade from Xenial past an unsupported release
+ not possible to upgrade from Xenial and jump over an unsupported release
Launchpad Janitor (janitor) wrote :

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

---------------
ubuntu-release-upgrader (1:17.10.4) artful; urgency=medium

  * Create demoted.cfg.xenial and DistUpgrade.cfg.xenial so that upgrades from
    Ubuntu 16.04 to Ubuntu 17.10 are supported. (LP: #1692092)

 -- Brian Murray <email address hidden> Fri, 19 May 2017 14:04:13 -0700

Changed in ubuntu-release-upgrader (Ubuntu):
status: In Progress → Fix Released

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:17.04.8 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ubuntu-release-upgrader (Ubuntu Zesty):
status: In Progress → Fix Committed
tags: added: verification-needed
Brian Murray (brian-murray) wrote :

I updated the meta-release-proposed file on the server to point at the dist-upgrader in zesty-proposed and then ran through the test from the test case. I had to modify the cached meta-release-proposed file (since the we are verifying an SRU in -proposed) on my system to verify the SRU but after that the test passed.

bdmurray@clean-xenial-amd64:~$ do-release-upgrade -p
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,265 kB]
Fetched 1,266 kB in 0s (0 B/s)
authenticate 'yakkety.tar.gz' against 'yakkety.tar.gz.gpg'
extracting 'yakkety.tar.gz'

[screen is terminating]
bdmurray@clean-xenial-amd64:~$ vi ~/.cache/update-manager-core/meta-release-proposed
bdmurray@clean-xenial-amd64:~$ do-release-upgrade -p
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,268 kB]
Fetched 1,269 kB in 0s (0 B/s)
authenticate 'zesty.tar.gz' against 'zesty.tar.gz.gpg'
extracting 'zesty.tar.gz'

Additionally, when using the zesty tarball I did not receive an error about the upgrade path being unsupported.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

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

---------------
ubuntu-release-upgrader (1:17.04.8) zesty; urgency=medium

  * Create demoted.cfg.xenial and DistUpgrade.cfg.xenial so that upgrades from
    Ubuntu 16.04 to Ubuntu 17.04 are supported. (LP: #1692092)

 -- Brian Murray <email address hidden> Fri, 19 May 2017 10:31:43 -0700

Changed in ubuntu-release-upgrader (Ubuntu Zesty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for ubuntu-release-upgrader has completed successfully and the package has now been 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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers