Activity log for bug #2063464

Date Who What changed Old value New value Message
2024-04-25 15:31:21 Andreas Schildbach bug added bug
2024-04-25 20:47:59 Nick Rosbrook marked as duplicate 2054761
2024-04-25 20:48:29 Nick Rosbrook removed duplicate marker 2054761
2024-04-25 20:50:36 Nick Rosbrook bug task added ubuntu-release-upgrader (Ubuntu)
2024-04-25 20:50:42 Nick Rosbrook ubuntu-release-upgrader (Ubuntu): status New Incomplete
2024-04-25 20:50:44 Nick Rosbrook systemd (Ubuntu): status New Incomplete
2024-04-26 01:40:50 Andreas Schildbach tags amd64 apport-bug noble amd64 apport-bug apport-collected dist-upgrade noble
2024-04-26 01:40:50 Andreas Schildbach description 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) 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
2024-04-26 01:40:51 Andreas Schildbach attachment added CurrentDmesg.txt.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770659/+files/CurrentDmesg.txt.txt
2024-04-26 01:40:52 Andreas Schildbach attachment added JournalErrors.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770660/+files/JournalErrors.txt
2024-04-26 01:40:53 Andreas Schildbach attachment added ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770661/+files/ProcCpuinfoMinimal.txt
2024-04-26 01:40:54 Andreas Schildbach attachment added ProcEnviron.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770662/+files/ProcEnviron.txt
2024-04-26 01:40:55 Andreas Schildbach attachment added VarLogDistupgradeAptHistorylog.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770663/+files/VarLogDistupgradeAptHistorylog.txt
2024-04-26 01:40:56 Andreas Schildbach attachment added VarLogDistupgradeAptclonesystemstate.tar.gz https://bugs.launchpad.net/bugs/2063464/+attachment/5770664/+files/VarLogDistupgradeAptclonesystemstate.tar.gz
2024-04-26 01:40:57 Andreas Schildbach attachment added VarLogDistupgradeAptlog.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770665/+files/VarLogDistupgradeAptlog.txt
2024-04-26 01:40:58 Andreas Schildbach attachment added VarLogDistupgradeApttermlog.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770666/+files/VarLogDistupgradeApttermlog.txt
2024-04-26 01:40:59 Andreas Schildbach attachment added VarLogDistupgradeMainlog.txt https://bugs.launchpad.net/bugs/2063464/+attachment/5770667/+files/VarLogDistupgradeMainlog.txt
2024-04-26 14:02:59 Nick Rosbrook systemd (Ubuntu): status Incomplete New
2024-04-26 14:03:01 Nick Rosbrook ubuntu-release-upgrader (Ubuntu): status Incomplete New
2024-04-29 08:34:58 Julian Andres Klode description 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 [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
2024-04-29 10:42:46 Launchpad Janitor merge proposal linked https://code.launchpad.net/~juliank/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/465146
2024-04-29 11:11:01 Julian Andres Klode summary Package wasn't installed on upgrade from Jammy to Noble systemd-resolved wasn't installed on upgrade from Jammy to Noble
2024-04-29 11:11:14 Julian Andres Klode bug task deleted systemd (Ubuntu)
2024-04-29 11:11:19 Julian Andres Klode ubuntu-release-upgrader (Ubuntu): status New Fix Committed
2024-04-29 17:44:22 Mauricio Faria de Oliveira ubuntu-release-upgrader (Ubuntu): status Fix Committed In Progress
2024-04-29 17:44:45 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2024-04-29 19:23:41 Steve Langasek ubuntu-release-upgrader (Ubuntu Noble): status New Fix Committed
2024-04-29 19:23:42 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2024-04-29 19:23:43 Steve Langasek bug added subscriber SRU Verification
2024-04-29 19:23:46 Steve Langasek tags amd64 apport-bug apport-collected dist-upgrade noble amd64 apport-bug apport-collected dist-upgrade noble verification-needed verification-needed-noble
2024-05-16 13:39:49 Nick Rosbrook tags amd64 apport-bug apport-collected dist-upgrade noble verification-needed verification-needed-noble amd64 apport-bug apport-collected dist-upgrade noble verification-done verification-done-noble
2024-05-17 13:03:17 Launchpad Janitor ubuntu-release-upgrader (Ubuntu): status In Progress Fix Released
2024-05-21 17:08:53 Launchpad Janitor ubuntu-release-upgrader (Ubuntu Noble): status Fix Committed Fix Released
2024-05-21 17:09:04 Brian Murray removed subscriber Ubuntu Stable Release Updates Team