[
https://issues.apache.org/jira/browse/IGNITE-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy updated IGNITE-12999:
--------------------------------------
Description: After merging
[IGNITE-11094|https://issues.apache.org/jira/browse/IGNITE-11094] in
cloneDiscoverySpi input parameter was obtained every time from
getConfiguration(), but not from first node, as it should be. This behaviour
leads to instant failure of multijvm tests
GridCacheAtomicMultiJvmFullApiSelfTest and
GridCachePartitionedMultiJvmFullApiSelfTest. After merging
[IGNITE-12992|https://issues.apache.org/jira/browse/IGNITE-12992], this twist
doesn't work and configuration cloned from first node, as it should. So we must
set zk connection string explicitly. (was: After merging
[IGNITE-12992|https://issues.apache.org/jira/browse/IGNITE-12992] to master,
mentioned above test, that was initially broken, starts to fail in master. This
is because actual zk connection string was set, but not wrong. So node joins
and assertion fails. Fix is trivial.)
> Fix broken ZookeeperDiscoverySpiSslTest.testIgniteSslWrongPort
> --------------------------------------------------------------
>
> Key: IGNITE-12999
> URL: https://issues.apache.org/jira/browse/IGNITE-12999
> Project: Ignite
> Issue Type: Test
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Minor
>
> After merging
> [IGNITE-11094|https://issues.apache.org/jira/browse/IGNITE-11094] in
> cloneDiscoverySpi input parameter was obtained every time from
> getConfiguration(), but not from first node, as it should be. This behaviour
> leads to instant failure of multijvm tests
> GridCacheAtomicMultiJvmFullApiSelfTest and
> GridCachePartitionedMultiJvmFullApiSelfTest. After merging
> [IGNITE-12992|https://issues.apache.org/jira/browse/IGNITE-12992], this twist
> doesn't work and configuration cloned from first node, as it should. So we
> must set zk connection string explicitly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
