Comment 19 for bug 2063464

Revision history for this message
Nick Rosbrook (enr0n) wrote :

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