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

[v23.1.x] Fix for hang on node joining cluster in NodeOperationFuzzyTest.test_node_operations #12491

Closed
vbotbuildovich opened this issue Jul 27, 2023 · 3 comments
Assignees
Labels
kind/backport PRs targeting a stable branch

Comments

@vbotbuildovich
Copy link
Collaborator

Backport #8559 to branch v23.1.x. Note that this issue was created as a placeholder, since the original PR's commit(s) could not be automatically cherry-picked.
Here are the commands to execute:

git checkout v23.1.x
git checkout -b vbotbuildovich/backport-8559-v23.1.x-836
git cherry-pick -x 6e093f8d85b313193e48c189e859da2585ce8003

git push origin vbotbuildovich/backport-8559-v23.1.x-836
gh pr create \
  --title "[v23.1.x] Fix for hang on node joining cluster in `NodeOperationFuzzyTest.test_node_operations`" \
  --base "v23.1.x" \
  --label "kind/backport" \
  --head "vbotbuildovich/backport-8559-v23.1.x-836" \
  --draft \
  --repo "redpanda-data/redpanda" \
  --reviewer "mmaslankaprv" \
  --milestone "v23.1.x-next" \
  --body "Backport of PR https://github.com/redpanda-data/redpanda/pull/8559 "
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jul 27, 2023
@vbotbuildovich vbotbuildovich added this to the v23.1.x-next milestone Jul 27, 2023
@piyushredpanda
Copy link
Contributor

@graphcareful : this can be closed as well, yes?

@graphcareful
Copy link
Contributor

I did a little investigation, #8559 was closed not merged because the test was eventually removed from dev. The issue was also manifesting in another issue #9052. #9052 has recently reopened so it appears there may not be a fix yet.

Maybe we should close this backport as #8559 seems to not be the fix needed to resolve the issue and instead backport whatever ends up being the eventual solution?

@piyushredpanda
Copy link
Contributor

SGTM.

@BenPope BenPope removed this from the v23.1.x-next milestone Aug 30, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backport PRs targeting a stable branch
Projects
None yet
Development

No branches or pull requests

4 participants