-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disrupt_remove_node_then_add_node: AssertionError: retry is not supported for long running commands, always use it with retry=0 #9534
Labels
Bug
Something isn't working right
Comments
I found this error in both Azure & GCE runs, no AWS run where this happened in the last week |
fruch
added a commit
to fruch/scylla-cluster-tests
that referenced
this issue
Dec 12, 2024
in ecc2c7e `long_running=True` paramter was introduced, but it must come togther with `retry=0`, and that was forgotten Fixes: scylladb#9534
3 tasks
This was referenced Dec 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seen here (https://argus.scylladb.com/tests/scylla-cluster-tests/0bc52ea0-4703-4855-8ba2-51bead782590), but also in other runs. Seems like a nemesis bug
The text was updated successfully, but these errors were encountered: