do-release-upgrade -d does not work to upgrade to 20.04 LTS

[Jeff Lane ]

I am not able to upgrade a server running 18.04.4 (HWE stack) to 20.04 LTS. There was some discussion about this on the ubuntu-server mailing list and a suggestion was made to update/install ca-certificates as a workaround, referencing lp:1796940, however that does not resolve the issue.

Interestingly, last Friday, the day after release, I was able to start an upgrade from Bionic to Focal on a NUC at home but I was forced to use -d as do-release-upgrade recognized Focal as a development release the day AFTER release. BUT, now a week later, I am completely unable to upgrade to Focal at all using do-release-upgrade.

To verify, I did a fresh deployment of 18.04.4, fully updated it and then attempted to upgrade to focal using do-release-upgrade.

ubuntu@drapion:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
ubuntu@drapion:~$ apt-cache policy ca-certificates
ca-certificates:
  Installed: 20180409
  Candidate: 20180409
  Version table:
 *** 20180409 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
ubuntu@drapion:~$ sudo do-release-upgrade
Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS develoment release
set Prompt=normal in /etc/update-manager/release-upgrades.
ubuntu@drapion:~$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

I also tried setting Prompt=normal and that didn't make a difference either:
ubuntu@drapion:~$ sudo apt-get update && sudo apt-get dist-upgrade -y
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-security InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:5 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  amd64-microcode intel-microcode iucode-tool libdbus-glib-1-2 linux-headers-generic-hwe-18.04-edge linux-image-generic-hwe-18.04-edge thermald
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ubuntu@drapion:~$ sudo do-release-upgrade
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.
ubuntu@drapion:~$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Upgrades to the development release are only
available from the latest supported release.
ubuntu@drapion:~$ sudo do-release-upgrade -p
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

ubuntu@drapion:~$ sudo dpkg -l |grep upgrade
ii  python3-distupgrade                    1:18.04.37                                      all          manage release upgrades
ii  ubuntu-release-upgrader-core           1:18.04.37                                      all          manage release upgrades
ii  unattended-upgrades                    1.1ubuntu1.18.04.14                             all          automatic installation of security upgrades
ii  update-manager-core                    1:18.04.11.12                                   all          manage release upgrades

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: User Name 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
Date: Sat May 2 06:00:38 2020
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.update-manager.release-upgrades: [modified]
mtime.conffile..etc.update-manager.release-upgrades: 2020-05-02T05:55:27.831107

[Jeff Lane  (bladernr)]

To clarify, I think this summarizes my expectation once a new LTS is released:

I would expect -d to still upgrade to Focal as a "development" release when 'Prompt=lts' is set.

On the day AFTER release (Apr 24), I was able to initiate an 18.04 -> 20.04 upgrade using 'do-release-upgrade -d' and today, I am unable to do so meaning if I WANT to update my bionic systems to focal now, I have no mechanism to do so at all.  I should be allowed to hang myself, accepting the risks of using -d in this context.

In other words,

Prompt=normal: `do-release-upgrade -d` should upgrade me from my release to the next development release (as soon as the development release is open for upgrading and testing).

Prompt=lts: `do-release-upgrade -d` should upgrade me from the last LTS to the current LTS in the GA to .1 window, and once the .1 release is done, then `do-release-upgrade` and `do-release-upgrade -d` should function identically.

[Steve Langasek (vorlon)]

Behavior seen here:

(bionic)$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1554 B]
Get:2 Upgrade tool [1344 kB]
Fetched 1346 kB in 0s (0 B/s)
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg'
extracting 'focal.tar.gz'

Reading cache

[...]

Your bug report shows that /etc/update-manager/release-upgrades but the file is not attached. What are its contents?

If you have Prompt=normal set in this file, this is the expected behavior.

If you have Prompt=lts set in the file, that is not the expected behavior; it IS expected that do-release-upgrade -d lets you upgrade to the newly-released LTS even though upgrades have not yet been turned on. And that's exactly the behavior I see here, so this bug is unreproducible for me.

[David Marzal (marzal)]

Same problem here:

LANG=C do-release-upgrade
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.

LANG=C do-release-upgrade -d
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.

/etc/update-manager/release-upgrades
# Default behavior for the release upgrader.

[DEFAULT]
# Default prompting and upgrade behavior, valid options:
#
# never - Never check for, or allow upgrading to, a new release.
# normal - Check to see if a new release is available. If more than one new
# release is found, the release upgrader will attempt to upgrade to
# the supported release that immediately succeeds the
# currently-running release.
# lts - Check to see if a new LTS release is available. The upgrader
# will attempt to upgrade to the first LTS release available after
# the currently-running one. Note that if this option is used and
# the currently-running release is not itself an LTS release the
# upgrader will assume prompt was meant to be normal.
Prompt=lts

[Steve Langasek (vorlon)]

What is the output when you run 'DEBUG_UPDATE_MANAGER=1 do-release-upgrade -d'?

[David Marzal (marzal)]

Sorry, I needed to use the computer and ended doing a clean install. This computer was a Kubuntu 18.04

I have migrated several Kubuntus 18.04 without problems even a Lubuntu 18.04 worked without problems with 'do-release-upgrade -d'.

So I can no longer be of assistant. If Jeff Lane is not able to do more testing I think the bug could be closed.

[Guillermo Gutiérrez (capitanterrex)]

I have the same issue here.

I think it would be resolved by updating this file in the ubuntu server, with adding an entry for 20.04:

https://changelogs.ubuntu.com/meta-release-lts

The most recent entry is for bionic at this moment.

That could be the problem?

[Guillermo Gutiérrez (capitanterrex)]

(I forgot to mention I have Prompt=lts in /etc/update-manager/release-upgrades )

[Steve Langasek (vorlon)]

> I think it would be resolved by updating this file in the ubuntu server, with adding an entry for 20.04:

That is not a solution to this bug. Upgrades have INTENTIONALLY not yet been turned on by default from 18.04 to 20.04; we do this only after the first point release of an LTS.

If you are running do-release-upgrade without the '-d' option, it is the expected behavior that you are not offered the upgrade.

If you are running do-release-upgrade /with/ the '-d' option, please provide the debugging information requested in comment #5.

I have updated the bug title to make it clear that this is about the behavior with -d.

[Guillermo Gutiérrez (capitanterrex)]

If that is the expected behaviour, ok.
But you can read the instructions to update 18.04LTS to 20.04LTS using Prompt=lts as in

https://wiki.ubuntu.com/FocalFossa/ReleaseNotes :

"""
To upgrade on a server system:

Install update-manager-core if it is not already installed.

Make sure the Prompt line in /etc/update-manager/release-upgrades is set to 'normal' if you want non-LTS upgrades, or 'lts' if you only want LTS upgrades.

Launch the upgrade tool with the command sudo do-release-upgrade

Follow the on-screen instructions.
"""

It says "sudo do-release-upgrade" not "sudo do-release-upgrade -d"

[Guillermo Gutiérrez (capitanterrex)]

(In my case using -d is currently updating to focal ;-)

[Steve Langasek (vorlon)]

On Fri, May 22, 2020 at 09:40:37AM -0000, Guillermo Gutiérrez wrote:
> If that is the expected behaviour, ok.

> But you can read the instructions to update 18.04LTS to 20.04LTS using
> Prompt=lts as in

> https://wiki.ubuntu.com/FocalFossa/ReleaseNotes

Right, it appears the release notes are currently inaccurate for upgrades
from 18.04. We'll fix this up.

[Launchpad Janitor (janitor)]

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]