-
Notifications
You must be signed in to change notification settings - Fork 589
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 (producer timeout) in NodesDecommissioningTest.test_decommissioning_cancel_ongoing_movements
#11751
Labels
Comments
7 tasks
7 tasks
9 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
7 tasks
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Jul 6, 2023
In current redpanda version node ids are dynamically assigned we can not use a node id as an index in the `RedpandaService` nodes list as it may result in incorrect results. In this particular example a node that was stopped was not the one that was decommissioned, leading to some of the rf=1 partitions being not available which prevented test from finishing. Fixes: redpanda-data#11751 Signed-off-by: Michal Maslanka <[email protected]>
7 tasks
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
Jul 6, 2023
In current redpanda version node ids are dynamically assigned we can not use a node id as an index in the `RedpandaService` nodes list as it may result in incorrect results. In this particular example a node that was stopped was not the one that was decommissioned, leading to some of the rf=1 partitions being not available which prevented test from finishing. Fixes: redpanda-data#11751 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 4ec279e)
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
Jul 6, 2023
In current redpanda version node ids are dynamically assigned we can not use a node id as an index in the `RedpandaService` nodes list as it may result in incorrect results. In this particular example a node that was stopped was not the one that was decommissioned, leading to some of the rf=1 partitions being not available which prevented test from finishing. Fixes: redpanda-data#11751 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 4ec279e)
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
Jul 6, 2023
In current redpanda version node ids are dynamically assigned we can not use a node id as an index in the `RedpandaService` nodes list as it may result in incorrect results. In this particular example a node that was stopped was not the one that was decommissioned, leading to some of the rf=1 partitions being not available which prevented test from finishing. Fixes: redpanda-data#11751 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 4ec279e)
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Jul 20, 2023
In current redpanda version node ids are dynamically assigned we can not use a node id as an index in the `RedpandaService` nodes list as it may result in incorrect results. In this particular example a node that was stopped was not the one that was decommissioned, leading to some of the rf=1 partitions being not available which prevented test from finishing. Fixes: redpanda-data#11751 Signed-off-by: Michal Maslanka <[email protected]> (cherry picked from commit 4ec279e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://buildkite.com/redpanda/redpanda/builds/32125#018901a0-d89b-41a7-924b-0c833bc6e8b9
The text was updated successfully, but these errors were encountered: