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

[Backport 6.2] fix(nemesis): disrupt_remove_node_then_add_node was missing retry=0 #9551

Merged
merged 1 commit into from
Dec 15, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Dec 15, 2024

in ecc2c7e long_running=True parameter was introduced, but it must come together with retry=0, and that was forgotten

Fixes: #9534

Testing

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)
  • Add unit tests to cover my changes (under unit-test/ folder)
  • Update the Readme/doc folder relevant to this change (if needed)

(cherry picked from commit e07010b)

Parent PR: #9546

in ecc2c7e `long_running=True` paramter
was introduced, but it must come togther with `retry=0`, and that
was forgotten

Fixes: #9534
(cherry picked from commit e07010b)
@mergify mergify bot assigned fruch Dec 15, 2024
@fruch fruch merged commit fc3707a into branch-6.2 Dec 15, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant