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

Fix the JVM we use for bwc nodes #46314

Merged

Conversation

alpar-t
Copy link
Contributor

@alpar-t alpar-t commented Sep 4, 2019

Before this change we would run bwc nodes with their bundled jdk if
these supported it, so the passed in runtime JDK was not honored.
This became obvius when running with FIPS.

Closes #41721

Before this change we would run bwc nodes with their bundled jdk if
these supported it, so the passed in runtime JDK was not honored.
This became obvius when running with FIPS.

Closes elastic#41721
@alpar-t alpar-t added :Delivery/Build Build or test infrastructure v8.0.0 v7.5.0 v7.4.1 labels Sep 4, 2019
@alpar-t alpar-t requested a review from jkakavas September 4, 2019 12:37
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

Copy link
Contributor

@mark-vieira mark-vieira left a comment

Choose a reason for hiding this comment

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

LGTM. Just so I understand though, this won't really have any effect on master, only in 7.x, yes?

@rjernst
Copy link
Member

rjernst commented Sep 4, 2019

Don't we always have runtime java home set in CI? Wouldn't this effectively eliminate testing of the bundled jdk?

@alpar-t
Copy link
Contributor Author

alpar-t commented Sep 5, 2019

@rjernst yes, it will. I'll prioritize #40531 to fix that. The alternative is to make this fips specific here ( set JAVA_HOME if running in a fips jvm ).
@mark-vieira it won't affect master because we aren't running with ClusterFormationTasks anymore since yesterday. That's not yet backpacked, but once it will we won't be testing the embedded JDK in CI anyhow, so we'll have to address that promptly.

@alpar-t alpar-t merged commit 074bc02 into elastic:master Sep 9, 2019
alpar-t added a commit that referenced this pull request Sep 9, 2019
Before this change we would run bwc nodes with their bundled jdk if
these supported it, so the passed in runtime JDK was not honored.
This became obvius when running with FIPS.

Closes #41721
alpar-t added a commit that referenced this pull request Sep 9, 2019
Before this change we would run bwc nodes with their bundled jdk if
these supported it, so the passed in runtime JDK was not honored.
This became obvius when running with FIPS.

Closes #41721
@colings86 colings86 added v7.4.0 and removed v7.4.1 labels Sep 11, 2019
@alpar-t alpar-t deleted the clusterformation-honor-runtime-java branch November 11, 2019 09:41
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v7.4.0 v7.5.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ci] corrupted keystore on java8 fips build
7 participants