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

[Rene Schickbauer]

"but this may be the right behavior, to install systemd-resolved"

In my case, systemd-resolved was installed before the upgrade, but it
was disables via command line. On updates and upgrades, i expect the
package manager to respect the configuration choices that have been made
previously.

do-release-upgrade asked a gazillion other questions if it should keep a
configuration or update it with the maintainers version. It *could* have
asked "Hey, i'm upgrading a service that's disabled. Do you want to a)
re-enable it, b) keep it disabled c) uninstall it completely".

-- 
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:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

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