de751cad03
The test simulates the cluster getting stuck during upgrade to raft topology due to majority loss, and then verifies that it's possible to get out of the situation by performing recovery and redoing the upgrade. Fixes: #17410 Closes scylladb/scylladb#17675 * https://github.com/scylladb/scylladb: test/topology_experimental_raft: add test_topology_upgrade_stuck test.py: bump minimum python version to 3.11 test.py: move gather_safely to pylib utils cdc: generation: don't capture token metadata when retrying update test.py: topology: ignore hosts when waiting for group0 consistency raft: add error injection that drops append_entries topology_coordinator: add injection which makes upgrade get stuck
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++ cqlpy - 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.