From 8984b50409304237bbb8524774aa59a7b0bcf249 Mon Sep 17 00:00:00 2001 From: Varun Yadav Date: Mon, 18 May 2026 19:15:50 +0530 Subject: [PATCH] fix: start_klusterlet_scenario action calls start instead of stop (#1324) The start_klusterlet_scenario branch in inject_managedcluster_scenario was calling stop_klusterlet_scenario on the scenarios object instead of start_klusterlet_scenario. Any user configuring this action would stop the klusterlet (scale to 0) instead of starting it (scale to 3). Fixes #1323 Signed-off-by: v0idheaven Co-authored-by: Paige Patton <64206430+paigerube14@users.noreply.github.com> --- .../managed_cluster/managed_cluster_scenario_plugin.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/krkn/scenario_plugins/managed_cluster/managed_cluster_scenario_plugin.py b/krkn/scenario_plugins/managed_cluster/managed_cluster_scenario_plugin.py index 474c4348..85372096 100644 --- a/krkn/scenario_plugins/managed_cluster/managed_cluster_scenario_plugin.py +++ b/krkn/scenario_plugins/managed_cluster/managed_cluster_scenario_plugin.py @@ -115,7 +115,7 @@ class ManagedClusterScenarioPlugin(AbstractScenarioPlugin): run_kill_count, single_managedcluster, timeout ) elif action == "start_klusterlet_scenario": - managedcluster_scenario_object.stop_klusterlet_scenario( + managedcluster_scenario_object.start_klusterlet_scenario( run_kill_count, single_managedcluster, timeout ) elif action == "stop_klusterlet_scenario":