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 2023.1] feature(nemesis): introduce lock for target selection #8491

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 28, 2024

since we run into multiple cases on parallel nemesis that there were multiple nemesis using the same node

we are introducing a lock over the selection of target nodes so we won't be able to pick it multiple times

Fixes: #6553

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 relevent to this change (if needed)

(cherry picked from commit 2a551db )

Parent PR: #7016

since we run into multiple cases on parallel nemesis
that there were multiple nemesis using the same node

we are introducing a lock over the selection of target nodes
so we won't be able to pick it multiple times

Fixes: #6553
(cherry picked from commit 2a551db)
@mergify mergify bot assigned fruch Aug 28, 2024
@fruch fruch merged commit 1418759 into branch-2023.1 Aug 28, 2024
7 checks passed
@mergify mergify bot deleted the mergify/bp/branch-2023.1/pr-7016 branch August 28, 2024 13:02
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