-
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
[Kerberos] Find if port is available before using it for Kdc server #36192
Conversation
If the randomly selected port was already in use the kerberos tests would fail. This commit adds check to see if the network port is available and if not continue to find one for kdc server. If it does not find port after 100 retries it throws an exception. Closes elastic#34261
Pinging @elastic/es-security |
I don't quite follow how this happens and/or how this will fix it.
I simply don't follow why this change is going to solve a problem if |
Yes, you are right the |
It doesn't make a lot of sense to use |
avoid use of `NetworkUtili#getServerPort()` function which does not correctly provide a random available port.
Instead of |
…lastic#36192) If the randomly selected port was already in use the Kerberos tests would fail. This commit adds check to see if the network port is available and if not continue to find one for KDC server. If it does not find port after 100 retries it throws an exception. Closes elastic#34261
If the randomly selected port was already in use the Kerberos
tests would fail. This commit adds check to see if the network
port is available and if not continue to find one for KDC server.
If it does not find port after 100 retries it throws an exception.
Closes #34261