Israel Fruchter

@cezarmoise please move to scylla core, I don't see how it's has anything todo with SCT

those happen cause other nemesis that change topology failed ``` 2025-01-24 08:14:41.747: (DisruptionEvent Severity.ERROR) period_type=end event_id=52869c52-b0e4-4b65-b6d0-e29c8f4e7ae0 duration=8m17s: nemesis_name=TerminateAndReplaceNode target_node=Node longevity-parallel-topology-schema--db-node-0b0e042d-6 [54.83.0.13 | 10.12.10.16] errors=Removed node state should be DN Traceback...

`disrupt_terminate_and_replace_node` need to be fixed to raise critical error on any case it can't do the replacement

> I don't understand what was the issue here. > The terminate nemesis node couldn't remove the node? > > It shouldn't raise a critical. If a nemesis terminates a...

Another option is to refactor this nemesis to make sure we move to the part adding node, regardless of what was failing. Either way, we can't accept a nemesis removing...

I would recommend add some linter that can identify those, and configure it specific to check those files in CI. I think ruff might be use to force adding type...

> My only issue is that `typing.*` are deprecated since 3.9, because now you can use inbuilt types for typing instead, e.g. `test: list[str] = []` > > See https://docs.python.org/3/library/typing.html#aliases-to-types-in-collections...

@mykaul, can we have someone to look at this one ? it still happening this week runs.

@mykaul still happening also this week and we aren't assigning it to anyone to further investigation...

I can confirm that pulling it with: ``` hydra investigate show-monitor aaa24776-6b4e-4302-ac21-c1eaafe22c31 ``` is working fine for me. @avikivity how are you trying to use the monitoring data ?