[Bug 2067800] Re: needrestart should avoid restarting runner-provisioner.service
Simon Chopin
2067800 at bugs.launchpad.net
Mon Jun 3 12:18:49 UTC 2024
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to needrestart in Ubuntu.
https://bugs.launchpad.net/bugs/2067800
Title:
needrestart should avoid restarting runner-provisioner.service
Status in needrestart package in Ubuntu:
New
Status in needrestart source package in Noble:
New
Status in needrestart source package in Oracular:
New
Bug description:
On GitHub action runners, if there is an update that causes
needrestart to restart the runner-provisioner.service, the action job
will immediately fail.
```
Restarting services...
/etc/needrestart/restart.d/systemd-manager
systemctl restart packagekit.service php8.3-fpm.service runner-provisioner.service systemd-journald.service systemd-networkd.service systemd-resolved.service systemd-udevd.service udisks2.service walinuxagent.service
Terminated
```
While the above shows multiple services being restarted,
"artificially" restarting just runner-provisioner.service has shown to
cause an immediate failure (as seen in
https://github.com/canonical/lxd-
ci/actions/runs/9323021640/job/25665299316?pr=178)
```
+ sudo systemctl restart runner-provisioner.service
Error: Process completed with exit code 143.
```
If needrestart has a way to exclude services from being restarted,
runner-provisioner.service should be added to the list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions
More information about the foundations-bugs
mailing list