Upgrade from 20.04 to 22.04.1 failed without error

[James Paton-Smith]

After being offered the upgrade to 22.04.1, I performed the upgrade. During the upgrade process, there were no errors at all.

When the upgrade was complete, it prompted me to restart the machine. The machine did get stuck trying to shutdown, but after about 5 minutes I performed a hard shutdown and powered it back up.

After powering on, the machine is still running Ubuntu 20.04.4

I will include the dist-upgrade logs.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.38
ProcVersionSignature: Ubuntu 5.14.0-1048.55-oem 5.14.21
Uname: Linux 5.14.0-1048-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 12 08:16:58 2022
InstallationDate: Installed on 2021-09-02 (343 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/usr/local/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2022-08-12 (0 days ago)
VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:

mtime.conffile..etc.update-manager.release-upgrades: 2022-08-04T08:58:52.146506

[James Paton-Smith (jamesps)]

Right, I think I found the cause of the issue. We are running puppet to manage our fleet of devices and it looks like there is a race condition here:

1 - Release upgrade starts and modifies the default sources lists (focal > jammy).
2 - If a puppet run starts before the actual upgrade begins (scheduled every hour by default), the sources list is reverted back to the current OS release (focal)
3 - The upgrade proceeds as though we're upgrading to 20.04.4, but it's already running this version and succeeds after a short time.

So this is entirely related to our configuration. Although I wonder if the ubuntu-release-upgrader package accounts for management tools like this, or if we simply need to manually disable Puppet before each upgrade?