-
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] SslMultiPortTests.testThatProfileTransportClientCanConnectToNoClientAuthProfile failure in master #37481
Labels
Comments
matriv
added
>test-failure
Triaged test failures from CI
:Security/TLS
SSL/TLS, Certificates
labels
Jan 15, 2019
Pinging @elastic/es-security |
jaymode
added a commit
to jaymode/elasticsearch
that referenced
this issue
Jan 15, 2019
This change fixes failures in the SslMultiPortTests where we attempt to connect to a profile on a port it is listening on but the connection fails. The failure is due to the profile being bound to multiple addresses and randomization will pick one of these addresses to determine the listening port. However, the address we get the port for may not be the address we are actually connecting to. In order to resolve this, the test now sets the bind host for profiles to the loopback address and uses the same address for connecting. Closes elastic#37481
jaymode
added a commit
that referenced
this issue
Jan 15, 2019
This change fixes failures in the SslMultiPortTests where we attempt to connect to a profile on a port it is listening on but the connection fails. The failure is due to the profile being bound to multiple addresses and randomization will pick one of these addresses to determine the listening port. However, the address we get the port for may not be the address we are actually connecting to. In order to resolve this, the test now sets the bind host for profiles to the loopback address and uses the same address for connecting. Closes #37481
jaymode
added a commit
that referenced
this issue
Jan 15, 2019
This change fixes failures in the SslMultiPortTests where we attempt to connect to a profile on a port it is listening on but the connection fails. The failure is due to the profile being bound to multiple addresses and randomization will pick one of these addresses to determine the listening port. However, the address we get the port for may not be the address we are actually connecting to. In order to resolve this, the test now sets the bind host for profiles to the loopback address and uses the same address for connecting. Closes #37481
jaymode
added a commit
that referenced
this issue
Jan 15, 2019
This change fixes failures in the SslMultiPortTests where we attempt to connect to a profile on a port it is listening on but the connection fails. The failure is due to the profile being bound to multiple addresses and randomization will pick one of these addresses to determine the listening port. However, the address we get the port for may not be the address we are actually connecting to. In order to resolve this, the test now sets the bind host for profiles to the loopback address and uses the same address for connecting. Closes #37481
jaymode
added a commit
that referenced
this issue
Jan 15, 2019
This change fixes failures in the SslMultiPortTests where we attempt to connect to a profile on a port it is listening on but the connection fails. The failure is due to the profile being bound to multiple addresses and randomization will pick one of these addresses to determine the listening port. However, the address we get the port for may not be the address we are actually connecting to. In order to resolve this, the test now sets the bind host for profiles to the loopback address and uses the same address for connecting. Closes #37481
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Console log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=sles/183/console
Errors:
Didn't manage to reproduce locally.
The text was updated successfully, but these errors were encountered: