** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
Marking won't fix as the resolution was in needrestart not cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
Closing cloud-init task for this bug as cloudimages created after
20240408 contain appropriate needrestart to defer cloud-final.service
during cloud-init package upgrade.
** Changed in: cloud-init (Ubuntu Noble)
Status: Confirmed => Won't Fix
--
You received this bug notification because
This bug was fixed in the package needrestart - 3.6-7ubuntu4
---
needrestart (3.6-7ubuntu4) noble; urgency=medium
* d/p/ubuntu-avoid-restart-cloud-final.patch:
- avoid automatic restart of cloud-init systemd oneshot services when
cloud-init invokes apt-get dist-upgrade
In foundations leadership sync on this today. I believe we determined
that the best course of action we should take at the moment is to pursue
an Ubuntu downstream needrestart patch to register cloud-init system
services as skipped during automatic restarts when apt commands are run
in
** Description changed:
Recent downstream ubuntu-specific changes in needrestart version
- 3.6-7ubuntu1 [1] set Ubuntu into autorestart mode during non-interactive
+ 3.6-7ubuntu1 [1] set Ubuntu into autorestart mode when non-interactive
apt-get dist-upgrade is being performed.
This
Just to recap some thoughts from the conversation cloud-init devs just
had:
- Automatically killing non-interactive processes may have far-reaching
changes. It may leave many packages besides cloud-init exposed. Any service
that calls `apt upgrade` etc non-interactively may get killed. How
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
preventing apt packages from being
:) Thanks again David for the context on your immediate workarounds you
would pursue here in the meantime while needrestart folks determine best
course of action for Ubuntu.
While I think one solution could be hard-appending all critical or
oneshot services of the world into upstream's
@chad.smith I used to use "NEEDRESTART_MODE=l" so needrestart would
print a list of suggested restarts and I could then run it interactively
if I needed to, but now I don't get a choice. needrestart always
restarts without asking.
So for now I put a bunch of processes to protect in a file in
> think the change at issue is adding the flags "-m u" to apt-pinvoke
in /etc/apt/apt.conf.d/99needrestart, which also means needrestart now
ignores a setting of "NEEDRESTART_MODE=l" in the environment when run
from apt.
@demyers I also saw this behavior too in initial testing and didn't
Thanks @demyers for context here too. I've just proposed the following
for cloud-final.service that seems to work on my side when testing in
lxd
https://code.launchpad.net/~chad.smith/ubuntu/+source/needrestart/+git/needrestart/+merge/463236
** Description changed:
Recent downstream
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/ubuntu/+source/needrestart/+git/needrestart/+merge/463236
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: needrestart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
I believe the patch referenced above causes other bad behaviors.
Specifically, it causes systemd-networkd to be restarted without any
sort of prompt whenever a library it links with receives a security
update. In my experience restarting systemd-networkd can break active
WireGuard tunnels and can
15 matches
Mail list logo
