Ensure that libvirtd is started after any enabled tcp/tls sockets #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m-bull
force-pushed
the
systemd-socket-deps
branch
2 times, most recently
from
e58efb5 to
202d0c4
Compare
This role restarts systemd services in the correct order, but after a subsequent reboot, libvirtd may start before the socket services, resulting in a broken libvirtd. Ensure that the correct startup order is followed by creating a systemd drop-in that forces libvirtd to start after any enabled systemd sockets.
m-bull
force-pushed
the
systemd-socket-deps
branch
from
202d0c4 to
a6dc366
Compare
|
This is similar to #66. Did you have that commit: https://github.com/stackhpc/ansible-role-libvirt-host/pull/67/files when you hit this? |
|
This doesn't work - just chucked it up for testing in the end. The real answer is modular vs monolithic daemon systemd services - working through this now. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This role restarts systemd services in the correct order, but after a subsequent reboot, libvirtd may start before the socket services, resulting in a broken libvirtd. Ensure that the correct startup order is followed by creating a systemd drop-in that forces libvirtd to start after any enabled systemd sockets.