f331d3b876
Before this change, it was ensured that a default superuser is created before serving CQL. However, the mechanism didn't wait for default password initialization, so effectively, for a short period, customer couldn't authenticate as the superuser properily. The purpose of this change is to improve the superuser initialization mechanism to wait for superuser default password, just as for the superuser creation. This change: - Introduce authenticator::ensure_superuser_is_created() to allow waiting for complete initialization of super user authentication - Implement ensure_superuser_is_created in password_authenticator, so waiting for superuser password initialization is possible - Implement ensure_superuser_is_create in transitional_authenticator, so the implementation from password_authenticator is used - Implement no-op ensure_superuser_is_create for other authenticators - Extend service::ensure_superuser_is_created to wait for superuser initialization in authenticator, just as it was implemented earlier for role_manager - Add injected error (sleep) in password_authenticator::start to reproduce a case of delayed password creation - Implement test_delayed_deafult_password to verify the correctness of the fix - Ensure superuser is created in single_node_cql_env::run_in_thread to make single_node_cql more similar to scylla_main in main.cc Fixes scylladb/scylladb#20566 Backport not needed - a minor bugfix Closes scylladb/scylladb#22532 * github.com:scylladb/scylladb: test: implement test_auth_password_ensured test: implement connect_driver argument in ManagerClient::server_add auth: ensure default superuser password is set before serving CQL auth: added password_authenticator_start_pause injected error
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.