From aa0af65152a8e6bc53bc33f4bb7c46336156f19f Mon Sep 17 00:00:00 2001 From: Israel Fruchter Date: Thu, 12 Dec 2024 17:03:39 +0200 Subject: [PATCH] fix(nemesis): `disrupt_remove_node_then_add_node` was missing retry=0 in ecc2c7e64206a1c4a465873c5c38caa66e2dbde4 `long_running=True` paramter was introduced, but it must come togther with `retry=0`, and that was forgotten Fixes: #9534 --- sdcm/nemesis.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdcm/nemesis.py b/sdcm/nemesis.py index aa46cefd5d..4c385fa367 100644 --- a/sdcm/nemesis.py +++ b/sdcm/nemesis.py @@ -3688,7 +3688,7 @@ def remove_node(): .format(rnd_node.ip_address, host_id)) with adaptive_timeout(Operations.REMOVE_NODE, rnd_node, timeout=HOUR_IN_SEC * 48): res = rnd_node.run_nodetool("removenode {}".format( - host_id), ignore_status=True, verbose=True, long_running=True) + host_id), ignore_status=True, verbose=True, long_running=True, retry=0) if res.failed and re.match(removenode_reject_msg, res.stdout + res.stderr): raise Exception(f"Removenode was rejected {res.stdout}\n{res.stderr}")