ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8619) Remote node could not start in ssh connection
Date Mon, 24 Sep 2018 13:43:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625839#comment-16625839
] 

Dmitriy Pavlov commented on IGNITE-8619:
----------------------------------------

[~ivanan.fed] [~SomeFire] it may be unrelated failure, so rerun of one suite may be perfectly
ok

> 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)

Mime
View raw message