Sergey Korotkov created IGNITE-17421:
----------------------------------------
Summary: [ducktests] discovery test broken
Key: IGNITE-17421
URL: https://issues.apache.org/jira/browse/IGNITE-17421
Project: Ignite
Issue Type: Test
Reporter: Sergey Korotkov
Changes in scope of the IGNITE-17322 break the "drop network" functionality
(used in the discovery ducktest for example) with the following exception:
{{
AttributeError: 'TcpCommunicationSpi' object has no attribute 'port_range'
self._target(*self._args, **self._kwargs)
File
"/opt/ignite-dev/modules/ducktests/tests/ignitetest/services/utils/ignite_aware.py",
line 357, in __exec_on_node
task(node)
File
"/opt/ignite-dev/modules/ducktests/tests/ignitetest/services/utils/ignite_aware.py",
line 387, in <lambda>
return self.exec_on_nodes_async(nodes, lambda n: self.__enable_netfilter(n,
net_part))
File
"/opt/ignite-dev/modules/ducktests/tests/ignitetest/services/utils/ignite_aware.py",
line 393, in __enable_netfilter
cm_ports = str(cm_spi.port) if cm_spi.port_range < 1 else str(cm_spi.port)
+ ':' + str(
AttributeError: 'TcpCommunicationSpi' object has no attribute 'port_range'
}}
The problem was not detected because exception raised in an async background
thread wasn't not logged to any log file included into the ducktests result zip
file. And was only visible in console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
