Skip to content
Snippets Groups Projects
Verified Commit ddbad4b4 authored by Christian Ehrhardt's avatar Christian Ehrhardt
Browse files

systemd: do not restart sockets


Sockets need to be started on install to be ready (drop --no-start), but not
stopped/restarted (add --no-stop-on-upgrade, drop --no-restart-after-upgrade)
later on to prevent issues on upgrade (on running services) or reinstall
(breaking the .sockets state)

Details:
- drop --no-start:
   .socket removed without being stopped will enter a faulty state that can only
   be recovered with a restart of the socket. We restart the service (libvirtd)
   backing the sockets anyway, the sockets can and should stay up as-is.
- drop --no-restart-after-upgrade:
   `--no-restart-after-upgrade` does not prevent restarts. It only controls
   when the restart happens, but we want no restart at-all so drop it.
- add --no-stop-on-upgrade:
   This needs to be added to not touch the .sockets state at all on
   upgrades.

LIBVIRT_NOSTART_UNITS nowadays only includes SOCKETS and their handling is
rather special, so this changes the name to LIBVIRT_SOCKETS to be more obvious
when touching d/rules

Signed-off-by: default avatarChristian Ehrhardt <christian.ehrhardt@canonical.com>
parent 295944dc
No related branches found
No related tags found
Loading
Pipeline #229495 passed
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment