[
https://issues.apache.org/jira/browse/IGNITE-21150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800329#comment-17800329
]
Maksim Timonin commented on IGNITE-21150:
-----------------------------------------
Core reason of the failure on TeamCity2:
# Test uses default IgniteConfiguraiton with Multicast IP Finder for
DiscoverySPI
# Default address resolved as 172.17.0.1 (docker interface). See
IgniteUtils#resetLocalHost - it collects all interfaces, and choose first one
by alphabet (docker0, ens160, lo).
# Multi cast is disabled for 172.* addresses on TC.
Ask admin (Vitaly Osipov) to sync network settings with TC1 (the test works on
TC1).
> Fix test CacheFutureExceptionSelfTest#testAsyncCacheFuture
> ----------------------------------------------------------
>
> Key: IGNITE-21150
> URL: https://issues.apache.org/jira/browse/IGNITE-21150
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The test fails on TC in 98% of runs [1]. Reason is wrong IgniteConfiguration.
> Tests must inherit settings of IgniteConfiguration from
> GridCommonAbstractTest for correct DiscoverySpi configuration.
>
> [13:39:43]W: [org.apache.ignite:ignite-core] WARNING: IP finder returned
> empty addresses list. Please check IP finder configuration and make sure
> multicast works on your network. Will retry every 2000 ms. Change
> 'reconnectDelay' to configure the frequency of retries.
> TC has limitations on multicast.
>
> [1]
> [https://ci2.ignite.apache.org/test/-8659993769955206328?currentProjectId=IgniteTests24Java8&expandTestHistoryChartSection=true]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
