[
https://issues.apache.org/jira/browse/IGNITE-22605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-22605:
------------------------------------
Description:
There is a flaky test
{code:java}
TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst{code}
Connection might close on writing header or message to the open socket. It
might happen due to a recipient ultimately closes connection on SSL handshake.
In a such case sender decides that connection can't be established due to no
alive nodes are exist. It starts creating own topology instead of failing with
SSL error.
Instead, node should additionally check a socket for SSL errors.
was:
There is a flaky test
TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst
Connection might fail on writing to the open socket while writing header or
message. It might happen due to a receipent ultimately close connection on SSL
handshake. The sender make a wrong decision that there is no cluster at all and
it's a first node.
> Wrong certificate chain might lead to split brain
> -------------------------------------------------
>
> Key: IGNITE-22605
> URL: https://issues.apache.org/jira/browse/IGNITE-22605
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
> Fix For: 2.17
>
>
> There is a flaky test
>
> {code:java}
> TcpDiscoverySslTrustedUntrustedTest#testMismatchingCaFirst{code}
>
> Connection might close on writing header or message to the open socket. It
> might happen due to a recipient ultimately closes connection on SSL
> handshake. In a such case sender decides that connection can't be established
> due to no alive nodes are exist. It starts creating own topology instead of
> failing with SSL error.
> Instead, node should additionally check a socket for SSL errors.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
