[
https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625253#comment-16625253
]
Oleg Ignatenko commented on IGNITE-8619:
----------------------------------------
[~ivanan.fed] yeah I also noticed that tests are not yet 100% stable when I
tried them on Teamcity. I preferred simpler version (without additional
connection attempts) only because at this point there seem to be not enough
evidence that this will really fix things (as I wrote before, there is a chance
that reason of failures is some infrastructure issue at Teamcity that we
haven't yet discovered).
I still feel that at this point it is too early to add additional connection
attempts in tests. However I do not insist on that and if you believe that it
is really necessary I will be fine if you add these.
> Remote node could not start in ssh connection
> ---------------------------------------------
>
> Key: IGNITE-8619
> URL: https://issues.apache.org/jira/browse/IGNITE-8619
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Ivan Fedotov
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Now there is a problem with launch remote node via ssh. Initially was an
> assumption that it's due to remote process has not enough time to write
> information into log:
> [IGNITE-8085|https://issues.apache.org/jira/browse/IGNITE-8085]. But this
> correction didn't fix [TeamCity
> |https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&tab=testDetails]
> (IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls).
> So it's necessary to make launch remote node via ssh always succesful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
