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

Restore printing bootstrap checks as errors #93178

Merged
merged 3 commits into from
Jan 24, 2023

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Jan 23, 2023

Bootstrap check failures were unintentionally moved to the info level in the log output. This commit restores logging them as errors.

closes #93074

Bootstrap check failures were unintentionally moved to the info level
in the log output. This commit restores logging them as errors.

closes elastic#93074
@rjernst rjernst added >bug :Core/Infra/CLI CLI utilities, scripts, and infrastructure v8.7.0 labels Jan 23, 2023
@rjernst rjernst requested a review from grcevski January 23, 2023 21:49
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Jan 23, 2023
@elasticsearchmachine
Copy link
Collaborator

Hi @rjernst, I've created a changelog YAML for you.

@@ -71,10 +71,10 @@ Environment environment() {
return nodeEnv.get();
}

void exitWithUserException(int exitCode, Exception e) {
err.print(USER_EXCEPTION_MARKER);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The stderr pump thread looks for this marker, I wonder if this changes that behaviour?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It slightly changes the error path, but it effectively doesn't change the result because the pump still exits after the stream is closed, which happens when we exit the main process.

I plan to create a followup to remove USER_EXCEPTION_MARKER as it is now no longer used.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I see now, the error pump finally has the latch decrement.

Copy link
Member

@thecoop thecoop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@grcevski grcevski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rjernst rjernst merged commit 54fe770 into elastic:main Jan 24, 2023
@rjernst rjernst deleted the startup/bootstrap_checks branch January 24, 2023 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Core/Infra/CLI CLI utilities, scripts, and infrastructure Team:Core/Infra Meta label for core/infra team v8.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bootstrap check failures are easy to miss in logs
4 participants