Skip to content

[CI] SSLErrorMessageFileTests class failing #127193

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

Open
elasticsearchmachine opened this issue Apr 22, 2025 · 2 comments
Open

[CI] SSLErrorMessageFileTests class failing #127193

elasticsearchmachine opened this issue Apr 22, 2025 · 2 comments
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Apr 22, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:security:test" --tests "org.elasticsearch.xpack.ssl.SSLErrorMessageFileTests.testMessageForCertificateAuthoritiesOutsideConfigDir" -Dtests.seed=D3D2ABE62CC59652 -Dtests.locale=sg-CF -Dtests.timezone=Pacific/Niue -Druntime.java=22

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a throwable with message of "failed to load SSL configuration [xpack.http.ssl] - cannot read configured PEM certificate_authorities [/this/path/is/outside/the/config/directory/file.error] because access to read the file is blocked; SSL resources should be placed in the [/dev/shm/bk/bk-agent-prod-gcp-1746506132293091251/elastic/elasticsearch-periodic/x-pack/plugin/security/build/testrun/test/temp/org.elasticsearch.xpack.ssl.SSLErrorMessageFileTests_D3D2ABE62CC59652-001/tempDir-020/config] directory"
     but: was <org.elasticsearch.ElasticsearchSecurityException: failed to load SSL configuration [xpack.http.ssl] - cannot read configured PEM certificate_authorities [/this/path/is/outside/the/config/directory/file.error] because the file does not exist> at org.elasticsearch.xpack.core.ssl.SSLService.lambda$loadSslConfigurations$11(SSLService.java:622)

Issue Reasons:

  • [8.19] 6 consecutive failures in class org.elasticsearch.xpack.ssl.SSLErrorMessageFileTests
  • [8.19] 20 consecutive failures in step openjdk22_checkpart4_java-matrix
  • [8.19] 20 consecutive failures in step graalvm-ce17_checkpart4_java-matrix
  • [8.19] 20 consecutive failures in step openjdk17_checkpart4_java-fips-matrix
  • [8.19] 20 consecutive failures in step openjdk23_checkpart4_java-matrix
  • [8.19] 20 consecutive failures in step openjdk21_checkpart4_java-matrix
  • [8.19] 20 consecutive failures in step openjdk17_checkpart4_java-matrix
  • [8.19] 120 failures in class org.elasticsearch.xpack.ssl.SSLErrorMessageFileTests (16.5% fail rate in 726 executions)
  • [8.19] 20 failures in step openjdk22_checkpart4_java-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in step graalvm-ce17_checkpart4_java-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in step openjdk17_checkpart4_java-fips-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in step openjdk23_checkpart4_java-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in step openjdk21_checkpart4_java-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in step openjdk17_checkpart4_java-matrix (100.0% fail rate in 20 executions)
  • [8.19] 20 failures in pipeline elasticsearch-periodic (100.0% fail rate in 20 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Security/Security Security issues without another label >test-failure Triaged test failures from CI Team:Security Meta label for security team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 22, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-security (Team:Security)

@jfreden
Copy link
Contributor

jfreden commented Apr 23, 2025

This looks similar to #121960. Will set to low-risk since it's a test only issue.

@jfreden jfreden added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants