[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:24.10.3

---------------
ubuntu-release-upgrader (1:24.10.3) oracular; urgency=medium

  [ Nick Rosbrook ]
  * tests: fix un-templated expected ubuntu.sources
  * DistUpgradeQuirks: prevent upgrades of TPM FDE desktops (LP: #2065229)
  * Run pre-build.sh: updating mirrors, demotions, and translations.

  [ Dave Jones ]
  * New quirk to add KMS overlay on Pi Server images (LP: #2065051)

 -- Nick Rosbrook <enr0n at ubuntu.com>  Thu, 09 May 2024 15:29:17 -0400

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/2063464

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

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Noble:
  Fix Committed

Bug description:
  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063464/+subscriptions