-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] CertificateGenerateToolTests testGeneratingSignedCertificates failing #72639
Labels
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Comments
benwtrent
added
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
labels
May 3, 2021
Pinging @elastic/es-security (Team:Security) |
tlrx
added a commit
that referenced
this issue
Jun 1, 2021
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jul 27, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jul 27, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359 Backport of: elastic#75718
tvernum
added a commit
that referenced
this issue
Jul 27, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: #75571, #75417, #75379, #72639, #72359 Backport of: #75718
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jul 28, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359 Backport of: elastic#75718
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Jul 28, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359 Backport of: elastic#75718
elasticsearchmachine
pushed a commit
that referenced
this issue
Jul 28, 2021
* Mute some security tests on problematic JDK8 build This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: #75571, #75417, #75379, #72639, #72359 Backport of: #75718 * Fix import
elasticsearchmachine
pushed a commit
that referenced
this issue
Jul 28, 2021
This commit adds some `assumeFalse` (or modifies exising ones) to mute tests on JDK 1.8.0_292 due to JDK-8266279 On this JDK build, a race condition sometimes causes the PBEWithSHA1AndDESede algorithm to appear as though it is unavailable. Relates: #75571, #75417, #75379, #72639, #72359 Backport of: #75718
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 15, 2022
We had muted specifc tests that were hit by JDK-8266279, by not allowing the tests to run on Java 1.8.0_292. We have since upgraded our Java 8 version in CI to Java 1.8.0_301 so the muting is irrelevant and can be removed Resolves elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359, elastic#75952, elastic#75718
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 15, 2022
We had muted specific tests that were hit by JDK-8266279, by not allowing the tests to run on Java 1.8.0_292. We have since upgraded our Java 8 version in CI to Java 1.8.0_301 so the muting is irrelevant and can be removed Resolves elastic#75571, elastic#75417, elastic#75379, elastic#72639, elastic#72359, elastic#75952, elastic#75718
Fixed in later jdk8 version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
It may be a combination of the OS + JVM version. I tried locally and it wasn't repeatable, but this failure looks similar to other security related failures due to unrecognized algorithms.
Build scan:
https://gradle-enterprise.elastic.co/s/spblrrxlqbg5o/tests/:x-pack:plugin:security:cli:test/org.elasticsearch.xpack.security.cli.CertificateGenerateToolTests/testGeneratingSignedCertificates
Reproduction line:
./gradlew ':x-pack:plugin:security:cli:test' --tests "org.elasticsearch.xpack.security.cli.CertificateGenerateToolTests.testGeneratingSignedCertificates" -Dtests.seed=D8985361EF945882 -Dtests.security.manager=true -Dtests.locale=ko -Dtests.timezone=Australia/North -Druntime.java=8
Applicable branches:
7.12
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.security.cli.CertificateGenerateToolTests&tests.test=testGeneratingSignedCertificates
Failure excerpt:
The text was updated successfully, but these errors were encountered: