Make munge daemon start depend on cloud-init final finishing#145
Open
Make munge daemon start depend on cloud-init final finishing#145
Conversation
m-bull
previously approved these changes
Aug 22, 2022
Contributor
m-bull
left a comment
m-bull
left a comment
There was a problem hiding this comment.
CI fail looks unrelated - LGTM
sjpb
force-pushed
the
feature/munge-cloud-init
branch
2 times, most recently
from
cc16f12 to
7dac372
Compare
sjpb
force-pushed
the
feature/munge-cloud-init
branch
from
7dac372 to
9a0d062
Compare
m-bull
approved these changes
Aug 22, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 allows cloud-init to inject the munge key, if desired. Without this a munge startup failure occurs complaining the munge key does not have enough bytes.