bootstrapper: stop join-client earlier #1268
Merged
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.
Proposed change(s)
This PR fixes a rare issue where the join-client of the bootstrapper of the initial control-plane node of a new cluster would try to join on itself:
constellation init
This is fixed by instead of deferring the call to
Clean()
in the init-server, we call the function after we acquired the node lock (same procedure as in the join-client).Additional Information
Log looks similar to the following