roachprod: fix roachprod start behaviour for single node clusters #51557
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
Fixes cockroachdb#51532. This is fallout from cockroachdb#51329, after which we tried using --join flags for single node clusters (that roachprod uses `start-single-node` for). This tripped up roachtests like cockroachdb#51532, which are now fixed. Release note: None.
|
This change is |
rafiss
approved these changes
Jul 17, 2020
There was a problem hiding this comment.
lgtm! thank you for the fix
Reviewed 1 of 1 files at r1.
Reviewable status:complete! 0 of 0 LGTMs obtained (waiting on @petermattis)
|
bors r=rafiss |
Build succeeded |
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.
Fixes #51532.
This is fallout from #51329, after which we tried using --join flags for
single node clusters (that roachprod uses
start-single-nodefor). Thistripped up roachtests like #51532, which are now fixed.
Release note: None.