Elasticsearch keystore test failures in JDK22 #104858
Comments
jan-elastic
added
:Security/Authorization
|
Pinging @elastic/es-security (Team:Security) |
|
This issue is reproducible on openjdk22 (which is not yet officially supported) and seems like a duplicate of #103963. |
slobodanadamovic
added
medium-risk
|
Another instance occurred today: https://gradle-enterprise.elastic.co/s/danbligjgug4q |
|
Another one at elasticsearch / periodic / main / openjdk22 / bwcTestSnapshots / java-matrix I'll mute the whole test suite since this is happening a lot lately! Security team, please revert the mute if that's not OK. |
|
many 8.12 & 7.17 test builds with JDK22 all just failed with issue.
JDK22 just isn't playing nice with this. I could list all the build failures, but the list would be rather long.
|
benwtrent
changed the title
benwtrent
added
blocker
:Core/Infra/Core
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
I am moving and relabeling this issue. Numerous test suites are failing JDK22 due to keystore exiting with a non-zero status. |
|
It looks like these are all the result of a change to Console in JDK 22 which we already addressed in #103614, but was not backported to 8.12 or 7.17. I'll work on backporting to those branches. |
Jdk 22 had test failures which caused this test to be muted. It looks like this bwc test may have failed because earlier ES versions had not yet had the necessary change to Terminal backported yet. That should be fixed now with elastic#106049 and elastic#106051. This commit re-enables the bwc test. relates elastic#104858
Jdk 22 had test failures which caused this test to be muted. It looks like this bwc test may have failed because earlier ES versions had not yet had the necessary change to Terminal backported yet. That should be fixed now with #106049 and #106051. This commit re-enables the bwc test. relates #104858
Jdk 22 had test failures which caused this test to be muted. It looks like this bwc test may have failed because earlier ES versions had not yet had the necessary change to Terminal backported yet. That should be fixed now with elastic#106049 and elastic#106051. This commit re-enables the bwc test. relates elastic#104858
|
Since the fix has been backported and we haven't seen issues, we're closing this as fixed. |
|
The re-enabled test is still failing for every bwc version - eg https://gradle-enterprise.elastic.co/s/uqjyfjzhvrcng/tests/task/:x-pack:plugin:security:qa:multi-cluster:v8.4.3%23bwcTest/details/org.elasticsearch.xpack.remotecluster.RemoteClusterSecurityBwcRestIT?top-execution=1 |
|
The issue seems to be that we're also forcing JDK 22 to run the old distributions in bwc tests. E.g. in this case |
…06559) We have instances where BWC tests configure old ES version nodes with the integTest distribution. This isn't a valid configuration, and while we in reality resolve the default distribution artifact, we have other configuration logic that behaves differently based on whether the integTest distro was _requested_. Specifically, what to set ES_JAVA_HOME to. This bug resulted in us attempting to run old nodes using the current bundled JDK version, which may be incompatible with that older version of Elasticsearch. Closes #104858
…astic#106559) We have instances where BWC tests configure old ES version nodes with the integTest distribution. This isn't a valid configuration, and while we in reality resolve the default distribution artifact, we have other configuration logic that behaves differently based on whether the integTest distro was _requested_. Specifically, what to set ES_JAVA_HOME to. This bug resulted in us attempting to run old nodes using the current bundled JDK version, which may be incompatible with that older version of Elasticsearch. Closes elastic#104858
…06559) (#106565) We have instances where BWC tests configure old ES version nodes with the integTest distribution. This isn't a valid configuration, and while we in reality resolve the default distribution artifact, we have other configuration logic that behaves differently based on whether the integTest distro was _requested_. Specifically, what to set ES_JAVA_HOME to. This bug resulted in us attempting to run old nodes using the current bundled JDK version, which may be incompatible with that older version of Elasticsearch. Closes #104858
Build scan:
https://gradle-enterprise.elastic.co/s/j2hllfv26rfzi/tests/:x-pack:plugin:security:qa:multi-cluster:v7.17.18%23bwcTest/org.elasticsearch.xpack.remotecluster.RemoteClusterSecurityBwcRestIT
Reproduction line:
Applicable branches:
main, 8.12
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.xpack.remotecluster.RemoteClusterSecurityBwcRestIT#classMethodFailure excerpt:
The text was updated successfully, but these errors were encountered: