-
Notifications
You must be signed in to change notification settings - Fork 579
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
CI Failure (connection failure in wait_for_removed) in RandomNodeOperationsTest.test_node_operations.enable_failures=True
#8576
Comments
This looks similar to: #8362 thought the exact symptom is a bit different: connection refused while connecting to a node while waiting for a node to be decommissioned. This run includes @mmaslankaprv's fixes in #8547, which included also changes to the ducktape side, so maybe this is the same underlying but with the ducktape-side stacks looking different now. |
Another failure observed here: https://ci-artifacts.dev.vectorized.cloud/redpanda/018612b9-546d-4b6b-b59a-110785a1d4f5/vbuild/ducktape/results/2023-02-02--001/report.html I took a quick look, I saw these two interesting logs:
Indicating that maybe all nodes were decomissioned? Later on I see this exception:
A crash when attempting to obtain the list of users, |
In the last failure the underlying issue will be solved by: #8568 |
The traceback here:
is caused by the fact that when test fails fuzzer is running after all redpanda nodes are stopped |
https://buildkite.com/redpanda/redpanda/builds/22336#018610d2-05ec-480e-83d5-d716ceac6f3d
Python backtraces:
The text was updated successfully, but these errors were encountered: