After investigating, I think the approach is to (1) update the deb-
systemd-helper state of systemd-resolved.service in jammy's
systemd.prerm, and (2) update the ubuntu-release-upgrader quirk as I
stated above.
Updating the tasks to reflect this, and will add SRU documentation.
** Also affects: dnsmasq (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: Ubuntu Jammy
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu Jammy)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
** Changed in: systemd (Ubuntu Jammy)
Status: New => Triaged
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => Won't Fix
** Changed in: ubuntu-release-upgrader (Ubuntu Jammy)
Status: New => Invalid
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
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:
Triaged
Status in dnsmasq package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
Invalid
Status in The Jammy Jellyfish:
New
Status in dnsmasq source package in Jammy:
Invalid
Status in systemd source package in Jammy:
Triaged
Status in ubuntu-release-upgrader source package in Jammy:
Invalid
Status in The Noble Numbat:
New
Status in dnsmasq source package in Noble:
Invalid
Status in systemd source package in Noble:
Won't Fix
Status in ubuntu-release-upgrader source package in Noble:
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
--
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
