Skip to content

Commit 247f648

Browse files
authored
Update titles and headings for consistency
1 parent e0cf4cd commit 247f648

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/operator-nexus/troubleshoot-kubernetes-cluster-stuck-workloads-due-to-power-failure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
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
33
description: Troubleshooting Nexus Kubernetes Cluster workloads stuck (unable to reschedule) on not-ready nodes due to bare-metal node power failure.
44
ms.service: azure-operator-nexus
55
ms.custom: troubleshooting
@@ -8,7 +8,7 @@ ms.date: 02/18/2025
88
ms.author: nyeemakhtar
99
author: mdnyeemakhtar
1010
---
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
1212

1313
What is a stuck workload?
1414

@@ -23,7 +23,7 @@ This guide details troubleshooting steps for cases where workloads on a Nexus Ku
2323
* Permissions to view Azure resources in the subscription where the Nexus Kubernetes Cluster is deployed
2424
* Necessary permissions to make changes using `kubectl` commands in Nexus Kubernetes Cluster (for example, deleting nodes)
2525

26-
## Diagnosing Stuck Workloads
26+
## Diagnose stuck workloads
2727

2828
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:
2929

@@ -47,7 +47,7 @@ If you observe that your applications aren't responding as expected, your worklo
4747

4848
![stuck workload on not-ready nodes](media/naks-workload-stuck-on-not-ready-nodes.png)
4949

50-
## Diagnosing Power Failure
50+
## Diagnose power failure
5151

5252
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.
5353

0 commit comments

Comments
 (0)