From eec3ad480ce1bbe44f109825a897257d86aaf766 Mon Sep 17 00:00:00 2001 From: Pedro Ielpi Date: Wed, 16 Apr 2025 11:33:25 +0200 Subject: [PATCH] M #-: Minor edits to Running K8s Clusters Signed-off-by: Pedro Ielpi --- .../running_kubernetes_clusters.rst | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/source/quick_start/usage_basics/running_kubernetes_clusters.rst b/source/quick_start/usage_basics/running_kubernetes_clusters.rst index c9e5414269..bca952781c 100644 --- a/source/quick_start/usage_basics/running_kubernetes_clusters.rst +++ b/source/quick_start/usage_basics/running_kubernetes_clusters.rst @@ -559,15 +559,16 @@ In this case you can manually instruct the VMs to report ``READY`` to the OneGat 3 oneadmin oneadmin OneKE 1.29 08/30 12:35:21 RUNNING -One or more VMs is Ready, but unreachable -++++++++++++++++++++++++++++++++++++++ +One or more VMs is Ready, but Unreachable ++++++++++++++++++++++++++++++++++++++++++++++ + +In a similar situation as above when ``onevm list`` shows all VMs running, but the service is still in ``DEPLOYING`` state and the VM is not reachable through SSH (e.g. to run the ``onegate vm update`` command). -In a similar situation as above when `onevm list`` shows all VMs running, but the service is still in ``DEPLOYING`` state, but the VM is not reachable through SSH (e.g. to run the ``onegate vm update`` command). +In this case, we can try to scale down and up the role of the problematic VM from Sunstone, the Front-end UI: -In this case, we can try to scale down and up the role of the problematic VM from the Front-end UI: - #. Go to Services in the Front-end UI and select the OneKE Service - #. In the Roles tab choose the problematic VM's role (e.g. worker) - #. Scale the role to 0 - #. Wait until shutdown of the VM, the scaling and cooldown period of the service finishes - #. Scale the role to 1 - #. Verify if the problem is solved and the ``oneflow list`` reports the ``RUNNING`` state + #. In Sunstone, go to **Services**, then select the **OneKE** Service. + #. In the **Roles** tab, choose the problematic VM's role (e.g. ``worker``). + #. Scale the role to ``0``. + #. Wait until VM shuts down and the scaling and cooldown period of the service finishes. + #. Scale the role to ``1``. + #. Verify if the problem is solved and ``oneflow list`` reports the ``RUNNING`` state.