-
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] LdapSessionFactoryTests testSslTrustIsReloaded failing #77024
Labels
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Comments
benwtrent
added
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
>test-failure
Triaged test failures from CI
labels
Aug 30, 2021
Pinging @elastic/es-security (Team:Security) |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Oct 26, 2021
Sometimes the final session seems to fail because it is still using the old trust configuration. This commit adds an assertBusy to give it time to settle. Resolves: elastic#77024
tvernum
added a commit
that referenced
this issue
Oct 28, 2021
Sometimes the final session seems to fail because it is still using the old trust configuration. This commit adds an assertBusy to give it time to settle. Resolves: #77024
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Oct 28, 2021
Sometimes the final session seems to fail because it is still using the old trust configuration. This commit adds an assertBusy to give it time to settle. Resolves: elastic#77024
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Oct 28, 2021
Sometimes the final session seems to fail because it is still using the old trust configuration. This commit adds an assertBusy to give it time to settle. Resolves: elastic#77024
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Oct 28, 2021
Sometimes the final session seems to fail because it is still using the old trust configuration. This commit adds an assertBusy to give it time to settle. Resolves: elastic#77024
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 28, 2021
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 28, 2021
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
This failure seems like a weird connection timeout. Unsure if its 100% the same as: #68995
But the cause
SSLPeerUnverifiedException(peer not authenticated), ldapSDKVersion=4.0.8,
may very well allow this issue to be merged into the other one.Build scan:
https://gradle-enterprise.elastic.co/s/xayth4e5nlihi/tests/:x-pack:plugin:security:test/org.elasticsearch.xpack.security.authc.ldap.LdapSessionFactoryTests/testSslTrustIsReloaded
Reproduction line:
./gradlew ':x-pack:plugin:security:test' --tests "org.elasticsearch.xpack.security.authc.ldap.LdapSessionFactoryTests.testSslTrustIsReloaded" -Dtests.seed=244C0CE1290F1309 -Dtests.locale=pl -Dtests.timezone=Asia/Dubai -Druntime.java=8
Applicable branches:
7.14
Reproduces locally?:
No
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.security.authc.ldap.LdapSessionFactoryTests&tests.test=testSslTrustIsReloaded
Failure excerpt:
The text was updated successfully, but these errors were encountered: