Skip to content
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 (raft_fixture.test_force_reconfiguration) in gtest_raft_rpunit #19938

Closed
nvartolomei opened this issue Jun 20, 2024 · 0 comments · Fixed by #20816
Closed

CI Failure (raft_fixture.test_force_reconfiguration) in gtest_raft_rpunit #19938

nvartolomei opened this issue Jun 20, 2024 · 0 comments · Fixed by #20816
Assignees
Labels
ci-rca/test CI Root Cause Analysis - Test Issue kind/bug Something isn't working rpunit unit test ci-failure (not ducktape)

Comments

@nvartolomei
Copy link
Contributor

nvartolomei commented Jun 20, 2024

https://buildkite.com/redpanda/redpanda/builds/50492#01903674-071e-459f-a5ca-0def42613a85

[ RUN      ] raft_fixture.test_force_reconfiguration
...
/var/lib/buildkite-agent/builds/buildkite-amd64-builders-i-063cb53df01607673-1/redpanda/redpanda/src/v/raft/tests/raft_reconfiguration_test.cc:628: Failure
Expected equality of these values:
  ec
    Which is: raft::errc:10
  errc::success
    Which is: raft::errc:0
...
[  FAILED  ] raft_fixture.test_force_reconfiguration (60606 ms)

First known hit in an unrelated PR #19937

JIRA Link: CORE-4267

@nvartolomei nvartolomei added kind/bug Something isn't working rpunit unit test ci-failure (not ducktape) labels Jun 20, 2024
@mmaslankaprv mmaslankaprv self-assigned this Jul 2, 2024
@mmaslankaprv mmaslankaprv added the ci-rca/test CI Root Cause Analysis - Test Issue label Jul 2, 2024
mmaslankaprv added a commit to mmaslankaprv/redpanda that referenced this issue Jul 2, 2024
Raft force reconfiguration test is designed to skip one of the nodes
when force updating configuration. In this scenario it may sometimes
happen that the node which wasn't updated with the configuration
override will become a leader. In this situation controller backend in
Redpanda will retry. Added retries to the test to make sure the test
will retry reconfiguration if it was reverted by node which was missing
update.

Fixes: redpanda-data#19938

Signed-off-by: Michał Maślanka <michal@redpanda.com>
mmaslankaprv added a commit to mmaslankaprv/redpanda that referenced this issue Jul 3, 2024
Raft force reconfiguration test is designed to skip one of the nodes
when force updating configuration. In this scenario it may sometimes
happen that the node which wasn't updated with the configuration
override will become a leader. In this situation controller backend in
Redpanda will retry. Added retries to the test to make sure the test
will retry reconfiguration if it was reverted by node which was missing
update.

Fixes: redpanda-data#19938

Signed-off-by: Michał Maślanka <michal@redpanda.com>
mmaslankaprv added a commit to mmaslankaprv/redpanda that referenced this issue Jul 3, 2024
Raft force reconfiguration test is designed to skip one of the nodes
when force updating configuration. In this scenario it may sometimes
happen that the node which wasn't updated with the configuration
override will become a leader. In this situation controller backend in
Redpanda will retry. Added retries to the test to make sure the test
will retry reconfiguration if it was reverted by node which was missing
update.

Fixes: redpanda-data#19938

Signed-off-by: Michał Maślanka <michal@redpanda.com>
mmaslankaprv added a commit to mmaslankaprv/redpanda that referenced this issue Jul 4, 2024
Raft force reconfiguration test is designed to skip one of the nodes
when force updating configuration. In this scenario it may sometimes
happen that the node which wasn't updated with the configuration
override will become a leader. In this situation controller backend in
Redpanda will retry. Added retries to the test to make sure the test
will retry reconfiguration if it was reverted by node which was missing
update.

Fixes: redpanda-data#19938

Signed-off-by: Michał Maślanka <michal@redpanda.com>
vbotbuildovich pushed a commit to vbotbuildovich/redpanda that referenced this issue Jul 4, 2024
Raft force reconfiguration test is designed to skip one of the nodes
when force updating configuration. In this scenario it may sometimes
happen that the node which wasn't updated with the configuration
override will become a leader. In this situation controller backend in
Redpanda will retry. Added retries to the test to make sure the test
will retry reconfiguration if it was reverted by node which was missing
update.

Fixes: redpanda-data#19938

Signed-off-by: Michał Maślanka <michal@redpanda.com>
(cherry picked from commit 30efad6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-rca/test CI Root Cause Analysis - Test Issue kind/bug Something isn't working rpunit unit test ci-failure (not ducktape)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants