-
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
Add await busy loop for SimpleKdcLdapServer initialization #39221
Merged
bizybot
merged 1 commit into
elastic:master
from
bizybot:ldap-check-listen-port-retry-kerberos-test
Feb 25, 2019
Merged
Add await busy loop for SimpleKdcLdapServer initialization #39221
bizybot
merged 1 commit into
elastic:master
from
bizybot:ldap-check-listen-port-retry-kerberos-test
Feb 25, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
>test-failure
Triaged test failures from CI
v7.0.0
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
v6.7.0
v8.0.0
v7.2.0
labels
Feb 21, 2019
Pinging @elastic/es-security |
jkakavas
added
>test
Issues or PRs that are addressing/adding tests
and removed
>test-failure
Triaged test failures from CI
labels
Feb 22, 2019
jaymode
approved these changes
Feb 22, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bizybot
added a commit
to bizybot/elasticsearch
that referenced
this pull request
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 pull request
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 pull request
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 pull request
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 pull request
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 pull request
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
Issues or PRs that are addressing/adding tests
v6.7.0
v7.0.0-rc1
v7.2.0
v8.0.0-alpha1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 reuseaddress to
true
on the socket so if the port that we found to be freeis in
TIME_WAIT
state it may fail to bind. As this is an internalclass 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