I reproduced this issue by: 1. Starting a Jammy LXD container 2. Stop+disable systemd-resolved, install dnsmasq 3. Verify that dnsmasq is healthy 4. Upgraded to Noble 5. systemd-resolved is running again, dnsmasq is broken
I started looking into this bug because it has a dnsmasq task (so it's part of the Ubuntu Server triage package set), but I believe the fix belongs to systemd. ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
