-
Notifications
You must be signed in to change notification settings - Fork 25k
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] Netty4HeadBodyIsEmptyIT testTemplateExists failing with FIPS enabled #71664
Comments
Pinging @elastic/es-security (Team:Security) |
Since this reproduces I've muted this test in |
This is another re-occurrence of #66820 and the root cause is that we use different distributions in regular and FIPS tests. We have an issue (#70005) for not mandating default distribution for FIPS tests and it should solve this problem for good. In the meantime, we could choose to either mute the test or raise another stop-gap fix. |
Cherry-picked Mark's mute from master into 7.x 8b32746 |
This test was fixed and unmuted in the main branch but remains muted in 7.x. The fix depends on changing the way FIPS test execute (#91101) and I don't want to introduce that change in 7.x to avoid wide sweeping changes in that patch branch. |
This is failing in our FIPS build, it reproduced locally for me with the FIPS flag set.
Build scan:
https://gradle-enterprise.elastic.co/s/h3dxshexqrzfi/tests/:modules:transport-netty4:javaRestTest/org.elasticsearch.rest.Netty4HeadBodyIsEmptyIT/testTemplateExists
Reproduction line:
./gradlew ':modules:transport-netty4:javaRestTest' --tests "org.elasticsearch.rest.Netty4HeadBodyIsEmptyIT.testTemplateExists" -Dtests.seed=A02E26474C28612C -Dtests.security.manager=true -Dtests.locale=en-GB -Dtests.timezone=Africa/Brazzaville -Druntime.java=11 -Dtests.fips.enabled=true
Applicable branches:
master
Reproduces locally?:
Yes
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.rest.Netty4HeadBodyIsEmptyIT&tests.test=testTemplateExists
Failure excerpt:
The text was updated successfully, but these errors were encountered: