This bug was fixed in the package systemd - 249.11-0ubuntu3.15
---
systemd (249.11-0ubuntu3.15) jammy; urgency=medium
* d/systemd.prerm: call d-s-h update-state for resolved on upgrades
(LP: #2078555)
systemd (249.11-0ubuntu3.14) jammy; urgency=medium
[ Ioanna Alifieraki ]
I have verified the fix using systemd from jammy-proposed. Since ubuntu-
release-upgrader was already accepted, I did not need to make any
changes to the upgrade step.
First, I installed systemd from jammy-proposed:
nr@six:~$ lxc launch ubuntu:jammy j
Launching j
nr@six:~$ lxc exec j bash
Hello Paul, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Just a quick note that I got hit by this a week or two ago, months after
moving from 22.04 to 24.04 and disabling sd-resolved by hand way back
then. IOW, it apparently happens on 24.04.0 -> 24.04.1 as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.26
---
ubuntu-release-upgrader (1:24.04.26) noble; urgency=medium
[ Erich Eickmeyer ]
* DistUpgradeQuirks: install pipewire-audio on ubuntu studio upgrades,
uninstalling pulseaudio and preventing install of
I have re-verified using 1:24.04.26 (although the new change was
unrelated to this one):
root@j:~# systemctl disable --now systemd-resolved
Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
root@j:~# s
Hello Paul, or anyone else affected,
Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.26
in a few hours, and then in the -proposed repository.
Please help us by testing this ne
Marking verified for noble so that we can move ubuntu-release-upgrader
along for 24.04.2, but we still need systemd in jammy before the bug is
fully fixed.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a me
I verified the ubuntu-release-upgrader portion of this by testing an
upgrade from jammy -> noble on a fresh LXD container:
root@j:~# systemctl disable --now systemd-resolved
Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.
Removed /etc/systemd/system/multi-user.target.wants/syste
Hello Paul, or anyone else affected,
Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.25
in a few hours, and then in the -proposed repository.
Please help us by testing this ne
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Milestone: None => ubuntu-24.04.2
--
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
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq i
** Description changed:
+ [Impact]
+
+ During upgrades, systemd-resolved will be started and enabled, even if it was
not previously. This is due to (a) the package split that made systemd-resolved
its own package (during kinetic cycle, hence between jammy and noble), and (b)
+ an ubuntu-release
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: d
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/479849
--
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
Titl
** Tags added: systemd-sru-next
** Also affects: dnsmasq (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status:
Given #11 and #12, which I agree with, I conclude that this is not a bug
in dnsmasq, so I'm marking its task as invalid.
** Changed in: dnsmasq (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
IIUC the problem is the package split of sd-resolved, which was still
part of the combined "systemd" binary package in Jammy. When people
upgrade to Noble "systemd" gets unconfigured, dropping any cache/state
about systemd-resolved.service, then the "systemd-resolved" binary
package gets (force)ins
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
** Tags added: foundations-todo
** Tags added: fr-9498
--
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
Stat
At this point, i fully expect for the systemd team to not lift a finger
as usual and i'm going to run into this major bug again in a couple of
years when upgrading to 26.04... :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Running into this in server triage as well, Just checking in to see if
someone is working on this bug?
--
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:
Upgrad
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
** Change
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
par
"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-rele
I'm running a different DNS solution, but i'm running into the same
problem with systemd-resolved
See bug 2078852
--
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
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
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.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
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/20
That command results in
"No pending crash reports. Try --help for more information."
What additional information would you like?
systemd-resolved would have been version 255.4-1ubuntu8.4.
dnsmasq is version 2.90-2build2
While systemd-resolved may be the new expected default, at least a
warning
Tagging for discussion, but this may be the right behavior, to install
systemd-resolved.
Please run
ubuntu-bug 2078555
to attach relevant information
** Tags added: rls-nn-incoming
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug n
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
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
32 matches
Mail list logo
