You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/troubleshoot-kubernetes-cluster-stuck-workloads-due-to-power-failure.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Troubleshooting Nexus Kubernetes Cluster stuck (unable to reschedule) workloads due to power failure
2
+
title: Troubleshoot Nexus Kubernetes Cluster Stuck (Unable to Reschedule) Workloads Due to Power Failure
3
3
description: Troubleshooting Nexus Kubernetes Cluster workloads stuck (unable to reschedule) on not-ready nodes due to bare-metal node power failure.
4
4
ms.service: azure-operator-nexus
5
5
ms.custom: troubleshooting
@@ -8,7 +8,7 @@ ms.date: 02/18/2025
8
8
ms.author: nyeemakhtar
9
9
author: mdnyeemakhtar
10
10
---
11
-
# Troubleshooting stuck (unable to reschedule) workloads in a Nexus Kubernetes Cluster due to power failure
11
+
# Troubleshoot stuck (unable to reschedule) workloads in a Nexus Kubernetes Cluster due to power failure
12
12
13
13
What is a stuck workload?
14
14
@@ -23,7 +23,7 @@ This guide details troubleshooting steps for cases where workloads on a Nexus Ku
23
23
* Permissions to view Azure resources in the subscription where the Nexus Kubernetes Cluster is deployed
24
24
* Necessary permissions to make changes using `kubectl` commands in Nexus Kubernetes Cluster (for example, deleting nodes)
25
25
26
-
## Diagnosing Stuck Workloads
26
+
## Diagnose stuck workloads
27
27
28
28
If you observe that your applications aren't responding as expected, your workloads might be stuck on the not-ready nodes. To diagnose stuck workloads on Nexus Kubernetes Cluster not-ready nodes, look for the following symptoms:
29
29
@@ -47,7 +47,7 @@ If you observe that your applications aren't responding as expected, your worklo
47
47
48
48

49
49
50
-
## Diagnosing Power Failure
50
+
## Diagnose power failure
51
51
52
52
Once you have confirmed that the workloads are stuck on the not-ready nodes, the next step will help you diagnose if Nexus Kubernetes Cluster nodes are not-ready due to power failure of one or more bare-metal machines.
0 commit comments