[Backport 6.2] fix(nemesis-target-pool): set method attribute for target pool #9527
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Decorator
disrupt_method_wrapper
rewrites target node pool and always set Nemesis.target_node_pool as data_nodes. This cause that target node is chosen from cluster.data_nodes always. This happemed because we have decorators chain:disrupt_method_wrapper -> target(data/zero/all)nodes -> disrupt*
Target node is chosen in
disrupt_method_wrapper
, and any changes in target_*_pool does not affect of target node if it is run in complex nemesis as SisyphusMonkey and also has affect in parallel nemesis runSet method attribute disrupt_*.target_pool for later use in decorator
disrupt_method_wrapper
, allows correctly set target pool for disrupt nemesisFixes: #9448
Used solution from pr: #9502
Testing
PR pre-checks (self review)
backport
labelsReminders
sdcm/sct_config.py
)unit-test/
folder)(cherry picked from commit 69ad0dd)
Parent PR: #9517