[Bug 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq

[Nick Rosbrook]

This is mostly a bug in the systemd/systemd-resolved postinst scripts
due to the package split, but we also need to fix the ubuntu-release-
upgrader quirk that disables the stub-resolver during upgrades from
jammy -> noble.

It needs a check that systemd-resolved is actually running, and
otherwise it should be a no-op.

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Incomplete => Triaged

-- 
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/2078555

Title:
  Upgrading from 22.04 to 24.04.01 breaks dnsmasq

Status in Ubuntu:
  Triaged
Status in dnsmasq package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Was running Ubuntu 22.04 as home gateway/firewall with dnsmasq as
  dns/dhcp server. Previous upgrade from Ubuntu 20.04 to 22.04 had
  worked without issue.

  After the upgrade to 24.04.01, systemd-resovled was automatically
  enabled. The result was that after a reboot, dnsmasq failed to start,
  as systemd-resolved had already bound to the necessary port. This in
  turn meant that my entire home network lost connectivity as it was
  dependant on dnsmasq running to provide both correct dns and dhcp
  functionality.

  Ideally, during the upgrade process, a check should be made for if
  another dns/dhcp service is already enabled, and if so, not enable
  systemd-resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2078555/+subscriptions