Yaron Gilor

@fgelcer , fixed conflict and added a background c-s thread during permission removal.

fixed nemesis count again.

> > which group owns the LDAP feature ? > > also how it is different from SLA nemesis, that works only on specific longevities ? or any other feature...

@fruch , i think it needs something to perhaps make it clearer to be different than the DB nodes core dump. so a different type can be good, perhaps even...

@roydahan , looks like it is reproduced on master. should we add more validations to the nemesis in order to clarify the status and what exactly it fails for? or...

possibly reproduced with Gemini as well in 5.0: error: ``` 2022-05-25 15:51:42.936: (DisruptionEvent Severity.ERROR) period_type=end event_id=7743865f-a457-4dc6-849a-a2e4526d9781 duration=2m37s: nemesis_name=DestroyDataThenRepair target_node=Node gemini-with-nemesis-3h-normal-5-0-db-node-357454a9-5 [3.239.33.160 | 10.0.0.221] (seed: False) errors=Data file for destroy is...

Reproduced with harry test: ``` Name: disrupt_rebuild_streaming_err Status: Failed Duration: 3 minutes, 14 seconds Failure reason Traceback (most recent call last): File "/home/ubuntu/scylla-cluster-tests/sdcm/nemesis.py", line 3669, in wrapper result = method(*args,...

@karol-kokoszka , it seems to be reproduced running 2023.1. can you please advise? is it ok for this manager-agent version? ( using "Scylla Manager Agent","version":"3.0.2-0.20221128.23e30739" ) ``` 2023-04-14 05:04:25.935 :...

reproduced in 2023.1 ics test 0e842a26-6b62-4164-ad08-513974539d88 as well.

The issue is not reproduced. Disk utilization is fine as well: