From a8a70fc6a0658fd3fa92f005e51da4cd73c15f7e Mon Sep 17 00:00:00 2001 From: Netram Faran Date: Mon, 1 Jun 2026 19:46:39 +0530 Subject: [PATCH] fix(node-actions): stop_start_kubelet_scenario calls restart_kubelet_scenario instead of node_reboot_scenario (#1368) Fixes #1367 Signed-off-by: netram75 Co-authored-by: Paige Patton <64206430+paigerube14@users.noreply.github.com> --- krkn/scenario_plugins/node_actions/abstract_node_scenarios.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/krkn/scenario_plugins/node_actions/abstract_node_scenarios.py b/krkn/scenario_plugins/node_actions/abstract_node_scenarios.py index 5f696bb9..c14a596d 100644 --- a/krkn/scenario_plugins/node_actions/abstract_node_scenarios.py +++ b/krkn/scenario_plugins/node_actions/abstract_node_scenarios.py @@ -103,6 +103,9 @@ class abstract_node_scenarios: def stop_start_kubelet_scenario(self, instance_kill_count, node, timeout): logging.info("Starting stop_start_kubelet_scenario injection") self.stop_kubelet_scenario(instance_kill_count, node, timeout) + # node_reboot_scenario is used intentionally: stopping the kubelet leaves the node NotReady, + # and oc debug cannot connect to a NotReady node, so restart_kubelet_scenario would fail. + # A hard reboot restarts the node and brings it back to Ready state. self.node_reboot_scenario(instance_kill_count, node, timeout) self.affected_nodes_status.merge_affected_nodes() logging.info("stop_start_kubelet_scenario has been successfully injected!")