Dmitriy Kruglov

DecommissionSeedNode nemesis is failing on Docker backend

4

DecommissionSeedNode test case is failing on Docker backend with the error: ``` Last events by severity CRITICAL - [60] 2024-04-08 12:52:28.274: (CassandraStressLogEvent Severity.CRITICAL) period_type=one-time event_id=d80834b5-1f7f-43e7-9ba7-c0371561612c during_nemesis=NodetoolSeedDecommission: type=OperationOnKey regex=Operation x10 on...

AddRemoveDcNemesis case is failing on Docker backend (local run) with the error: ``` ----- LAST ERROR EVENT ------------------------------------------------------- 2024-04-18 09:06:52.191: (DisruptionEvent Severity.ERROR) period_type=end event_id=0f2b5ecb-1042-4d08-8ec6-db8aec3e2f0a duration=6m28s: nemesis_name=AddRemoveDc target_node=Node longevity-1gb-1h-nemesis-dmitriy-db-node-febaa291-2 [172.17.0.4 |...

NodeRestartWithResharding and SoftRebootNodeMonkey nemeses fail on Docker backend, being unable to successfully finish a node reboot disruption

2

NodeRestartWithResharding and SoftRebootNodeMonkey nemeses fail on Docker backend, when waiting for a node to return back after reboot/restart disruption. The error during NodeRestartWithResharding nemesis: ``` 2024-04-08 18:39:07.166: (DisruptionEvent Severity.ERROR) period_type=end...

TerminateAndRemoveNodeMonkey nemesis is failing on Docker backend when trying to repair a node after disruption

2

TerminateAndRemoveNodeMonkey nemesis case is failing on attempts to repair a node after the disruption, with the error: ``` 04:20:59 < t:2024-04-09 02:20:58,809 f:nemesis.py l:3501 c:sdcm.nemesis p:ERROR > sdcm.nemesis.TerminateAndRemoveNodeMonkey: failed to...

RejectNodeExporterNetworkMonkey and RejectThriftNetworkMonkey nemeses depend on iptables and fail on its installation with the error: ``` 2024-04-08 21:51:33.338: (DisruptionEvent Severity.ERROR) period_type=end event_id=21d4fe27-19a9-47dc-9706-012b179a8206 duration=8m35s: nemesis_name=NetworkRejectNodeExporter target_node=Node longevity-1gb-1h-nemesis-longevit-db-node-918182cb-1 [172.17.0.3 | 172.17.0.3] (seed:...

'smp' scylla command line argument has no effect when cluster is created on docker backend

5

### Issue description Even though a specific value can be set for `--smp` option when starting scylla from command line, it has no effect if cluster is created on docker...

When encryption is enabled nemesis fails to start on Docker backend with `cp: cannot create regular file '/home/scylla-test/.cassandra/cqlshrc': Permission denied` error

4

### Issue description If encryption is enabled in test configuration, any nemesis fails on the step of client certificate installation: ``` Traceback (most recent call last): File "/home/dmitriy/Work/Scylla/scylla-cluster-tests/sdcm/cluster.py", line 3717,...

`PeersV2NodeRefreshIT#should_successfully_send_peers_v2_node_refresh_query` integration test does not close its test session, leading to leaks when integration tests suite is executed in CI. This affects `SessionLeakIT#should_warn_when_session_count_exceeds_threshold` test, which sees the leaked session and...

### Issue description When enforcing hostname validation, scylla-bench requires to provide server hostname for validation. If provided, only one server name is accepted/processed. When cluster nodes configured to have individual...

## Packages Scylla version: `2024.1.8-20240724.fc3e399a25f3` with build-id `646cf933d8926947ade5b2a7cbc5bacb145df4fb` Kernel Version: `5.15.0-1066-aws` ## Issue description During [enterprise-2024.1/longevity/longevity-multidc-schema-topology-changes-12h-test#26](https://argus.scylladb.com/test/8764d79e-d785-4b99-9c70-99e2f24d0a18/runs?additionalRuns[]=97c11d18-65ec-4dfa-9b9d-70ba669c3f11) test `disrupt_terminate_and_replace_node` and `disrupt_create_index` nemeses were started in parallel and were targeted onto the...