systemd-resolved wasn't installed on upgrade from Jammy to Noble

[Andreas Schildbach]

[Impact]
Upgrades from jammy to noble sometimes end up without systemd-resolved being installed, breaking networking as the system already migrated to resolved in jammy and now it disappears.

[Test plan]
Sadly we have so far been unable to reproduce the issue so we cannot provide a test plan to verify the fix right now. That said, the fix is the minimal "install it after marking the upgrades", so it should be obviously correct (TM).

[Where problems could occur]
Problems could be expected around Conflicts/Breaks from or to systemd-resolved.

systemd-resolved Provides and Conflicts with resolvconf, but it is the only provider in the archive. systemd-resolved has no other Conflicts.

There are no reverse-Breaks or reverse-Conflicts for systemd-resolved.

Other dependency issues could occur if the dependencies of systemd-resolved are unsatisfiable, however, systemd-resolved only requires essential packages, systemd packages, and a dbus system bus.

[Original bug report]
I just do-release-upgraded from Jammy to Noble on a pretty minimal server.

After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem.

So I assume this is a mistake in the upgrade process.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 255.4-1ubuntu8
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Apr 25 15:27:23 2024
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +0000:2024-04-25 15:32:14.747564766 +0000:/var/crash/_usr_bin_docker-compose.0.crash
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Tags: noble dist-upgrade
Uname: Linux 6.8.0-31-generic x86_64
UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago)
UserGroups: N/A
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting
_MarkForUpload: True

[Nick Rosbrook (enr0n)]

Sorry for the previous noise, I was on the wrong page. Can you please run apport-collect -p ubuntu-release-upgrader 2063464 so that upgrade logs are attached?

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Andreas Schildbach (schildbach)]

apport information

[Julian Andres Klode (juliank)]

Fix committed in ubuntu/main

[Mauricio Faria de Oliveira (mfo)]

Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.

(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should be interpreted as -proposed/Ubuntu Archive, not others.)

https://wiki.ubuntu.com/Bugs/Bug%20statuses

[Steve Langasek (vorlon)]

Hello Andreas, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.17 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, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted ubuntu-release-upgrader (1:24.04.17) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:24.04.17 (arm64, armhf, ppc64el, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#ubuntu-release-upgrader

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Timo Aaltonen (tjaalton)]

Hello Andreas, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.18 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, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Andreas Schildbach (schildbach)]

It's not clear to me how to test this package in the context of a `do-release-upgrade`. I tried both `-d` and `-p` to another minimal Jammy server install, but it both denied an upgrade with this message:

```
$ sudo 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.
```

The upgrade that caused this bug report (see "original report") was done using `-d` – this doesn't work any more at the moment.

[Nick Rosbrook (enr0n)]

As the test plan mentions, there is no known reproducer for this at the moment. The best I can do is confirm that the PostUpgradeInstall=systemd-resolved setting is present for upgrades from Jammy:

nr@six:/t/tmp.U3JgXkB0Vr$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-16 15:37:48-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.83, 91.189.91.82, 91.189.91.81, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.83|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: ‘noble.tar.gz’

noble.tar.gz 100%[================================================>] 1.21M 984KB/s in 1.3s

2024-05-16 15:37:50 (984 KB/s) - ‘noble.tar.gz’ saved [1274850/1274850]

nr@six:/t/tmp.U3JgXkB0Vr$ tar xf noble.tar.gz
nr@six:/t/tmp.U3JgXkB0Vr$ grep systemd-resolved DistUpgrade.cfg.jammy
PostUpgradeInstall=systemd-resolved