[
https://issues.apache.org/jira/browse/IGNITE-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625773#comment-16625773
]
Ignite TC Bot commented on IGNITE-8619:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1923569]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsDiskErrorsRecoveringTest.testRecoveringOnNodeStartMarkerWriteFail -
0,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1923608&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
