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.
On GitHub action runners, if there is an update that causes needrestart to restart the runner- provisioner. service, the action job will immediately fail.
``` rt/restart. d/systemd- manager provisioner. service systemd- journald. service systemd- networkd. service systemd- resolved. service systemd- udevd.service udisks2.service walinuxagent. service
Restarting services...
/etc/needresta
systemctl restart packagekit.service php8.3-fpm.service runner-
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/2566529931 6?pr=178)
``` provisioner. service
+ sudo systemctl restart runner-
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.