Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachprod: fix confusing start-up error #104777

Merged
merged 1 commit into from
Jun 14, 2023

Conversation

herkolategan
Copy link
Collaborator

@herkolategan herkolategan commented Jun 13, 2023

Starting a secure cluster locally does a check for certificates. In the event the certificates are not found, which is a valid case, an error is printed. The start command works correctly, but the error can cause confusion:

./bin/roachprod start local --secure
12:47:56 cluster_synced.go:2475: 0: COMMAND_PROBLEM: exit status 1
(1) COMMAND_PROBLEM
Wraps: (2) exit status 1
Error types: (1) errors.Cmd (2) *exec.ExitError:
local: initializing certs 1/1 /
local: distributing certs 2/2
12:47:59 cockroach.go:184: local: starting nodes

This change modifies the command to do a check without causing an error, and
also propagates any real errors that could occur while doing the check.

Epic: none

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@herkolategan herkolategan force-pushed the hbl/roachprod-start-error branch from 83c90b1 to 49cf35e Compare June 13, 2023 13:53
Starting a cluster locally does a check for certificates. In the event the
certificates are not found, which is a valid case, an error is printed. The
start command works correctly, but the error can cause confusion:

```bash
/bin/roachprod start local --secure 12:47:56 cluster_synced.go:2475: 0:
COMMAND_PROBLEM: exit status 1 (1) COMMAND_PROBLEM Wraps: (2) exit status 1
Error types: (1) errors.Cmd (2) *exec.ExitError: local: initializing certs 1/1 /
local: distributing certs 2/2
```

This change modifies the command to do a check without causing an error, and
also propagates any real errors that could occur while doing the check.
@herkolategan herkolategan force-pushed the hbl/roachprod-start-error branch from 282c25e to f0da5e8 Compare June 13, 2023 14:07
@herkolategan herkolategan marked this pull request as ready for review June 13, 2023 14:52
@herkolategan herkolategan requested a review from a team as a code owner June 13, 2023 14:52
@herkolategan herkolategan requested review from srosenberg and smg260 and removed request for a team June 13, 2023 14:52
@srosenberg srosenberg added the backport-23.1.x Flags PRs that need to be backported to 23.1 label Jun 13, 2023
@herkolategan
Copy link
Collaborator Author

bors r=srosenberg

@craig
Copy link
Contributor

craig bot commented Jun 14, 2023

Build succeeded:

@craig craig bot merged commit 3572499 into cockroachdb:master Jun 14, 2023
@blathers-crl
Copy link

blathers-crl bot commented Jun 14, 2023

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from f0da5e8 to blathers/backport-release-23.1-104777: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.1.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.1.x Flags PRs that need to be backported to 23.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants