You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aditya Mukhopadhyay (Jira)" <ji...@apache.org> on 2025/12/17 10:40:00 UTC

[jira] [Created] (IGNITE-27378) Fix tests that supply spurious network addresses to StaticNodeFinder

Aditya Mukhopadhyay created IGNITE-27378:
--------------------------------------------

             Summary: Fix tests that supply spurious network addresses to StaticNodeFinder
                 Key: IGNITE-27378
                 URL: https://issues.apache.org/jira/browse/IGNITE-27378
             Project: Ignite
          Issue Type: Bug
          Components: migration tools
    Affects Versions: 3.1
            Reporter: Aditya Mukhopadhyay
            Assignee: Tiago Marques Godinho


Recently, there was a change made to the {{StaticNodeFinder}} - it now throws an exception that causes a node to stop, if it cannot resolve any of the node addresses provided to it.

This is the ticket for this change: https://issues.apache.org/jira/browse/IGNITE-26910.

Unfortunately, this now leads to a regression in one of the tests in the migration tools configuration converter - [https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3x_Test_IntegrationTests_Mi[…]urationConverter/9814682?logFilter=debug&logView=flowAware|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3x_Test_IntegrationTests_MigrationToolsConfigurationConverter/9814682?logFilter=debug&logView=flowAware].
In this test, config like {{}}
{code:java}

{code}
{{nodeFinder{netClusterNodes=["node1:49500","node2:49500","node3:49500"],type=STATIC}}

 is supplied to the node. Since this consists of spurious node addresses, this test fails.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)