-
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] Test Failure ReloadSecureSettingsIT testWrongKeystorePassword #32411
Comments
Pinging @elastic/es-core-infra |
@jkakavas this may be related to FIPS. Can you take a look? |
I had it in my radar since yesterday ( https://groups.google.com/a/elastic.co/d/msg/build-elasticsearch/KMDL9V3yJi0/NGiG3OH1BwAJ ) . This is because of the change introduced here #31989 (comment) , and it looks that the behavior with BC is not consistent. I will take a closer look and adjust. |
This failed again in Since it's FIPS-only I haven't muted it as it won't interfere with PR builds or intake builds, but let me know if you'd prefer me to mute it. |
Thanks @droberts195 , I agree this is not worth muting. I will address this today. |
This problem is not entirely specific to this test, but this is the only test where we load a KeyStoreWrapper with a wrong password, hence it manifested here. I raised #32464 to fix the underlying issue, that will also mitigate the test failures here |
* Ensure decryption related exceptions are handled This commit ensures that all possible Exceptions in KeyStoreWrapper#decrypt() are handled. More specifically, in the case that a wrong password is used for secure settings, calling readX on the DataInputStream that wraps the CipherInputStream can throw an IOException. It also adds a test for loading a KeyStoreWrapper with a wrong password. Resolves elastic#32411
Console Link:
(https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java8fips,nodes=virtual&&linux/200/console)
Reproduce With:
Stack Trace:
The text was updated successfully, but these errors were encountered: