c0c291b985
In this PR we add the tests for two scenarios, related to the use of IPs in raft topology. * When the replaced node transitions to the `LEFT` state we used to remove the IP of such node from gossiper. If we replace with same IP, this caused the IP of the new node to be removed from gossiper. This problem was fixed by #16820, this PR adds a regression test for it. * When a node is restarted after decommissioning some other node, the restarting node tries to apply the raft log, this log contains a record about the decommissioned node, and we got stuck trying to resolve its IP. This was fixed by #16639 - we excluded IPs from the RAFt log application code and moved it entirely to host_id-s. This PR adds a regression test for this case. Closes scylladb/scylladb#15967 Closes scylladb/scylladb#14803 Closes scylladb/scylladb#17180 * github.com:scylladb/scylladb: test_topology_ops: check node restart after decommission test_replace_reuse_ip: check other servers see the IP
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cql-pytest - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.