-
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] testKerbTicketGeneratedForDifferentServerFailsValidation fails on 6.5 #35982
Labels
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
>test-failure
Triaged test failures from CI
Comments
jkakavas
added
>test-failure
Triaged test failures from CI
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
labels
Nov 28, 2018
Pinging @elastic/es-security |
@bizybot what is the status here? |
I looked at the CI failures since 28th November and there is no other build where this has failed. |
bizybot
pushed a commit
to bizybot/elasticsearch
that referenced
this issue
Feb 21, 2019
There have been intermittent failures where either ldap server could not be started or kdc server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in a await busy loop and fail after 10 seconds if not initialized. Closes elastic#35982
bizybot
added a commit
to bizybot/elasticsearch
that referenced
this issue
Feb 25, 2019
…9221) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes elastic#35982
bizybot
added a commit
to bizybot/elasticsearch
that referenced
this issue
Feb 25, 2019
…9221) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes elastic#35982
bizybot
added a commit
to bizybot/elasticsearch
that referenced
this issue
Feb 25, 2019
…9221) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes elastic#35982
bizybot
added a commit
to bizybot/elasticsearch
that referenced
this issue
Feb 25, 2019
…9221) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes elastic#35982
bizybot
added a commit
that referenced
this issue
Feb 25, 2019
…39344) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes #35982
bizybot
added a commit
that referenced
this issue
Feb 25, 2019
…39343) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes #35982
bizybot
added a commit
that referenced
this issue
Feb 25, 2019
…39342) There have been intermittent failures where either LDAP server could not be started or KDC server could not be started causing failures during test runs. `KdcNetwork` class from Apache kerby project does not set reuse address to `true` on the socket so if the port that we found to be free is in `TIME_WAIT` state it may fail to bind. As this is an internal class for kerby, I could not find a way to extend. This commit adds a retry loop for initialization. It will keep trying in an await busy loop and fail after 10 seconds if not initialized. Closes #35982
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)
>test-failure
Triaged test failures from CI
Build https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.5+multijob-darwin-compatibility/67/console
failed when KDC failed to connect to the in memory ldap server. I can't reproduce this locally so it could be a transient error but I'm opening this so that we take a look at least. Initially, it felt this has something to do with #35764 but this wasn't backported to 6.5 so it should be irrelevant.
Stacktrace:
The text was updated successfully, but these errors were encountered: