// Module included in the following assemblies:
//
// * post_installation_configuration/day_2_core_cnf_clusters/updating/update-rhacm-talm-troubleshooting.adoc

:_mod-docs-content-type: PROCEDURE
[id="core-cluster-upgrade-ts-nodes-notready_{context}"]
= Diagnosing worker nodes stuck in NotReady state

[role="_abstract"]
If worker nodes show `NotReady` status during an update, common causes include disk pressure, memory pressure, network connectivity issues, and PID pressure.

.Prerequisites

* You have worker nodes showing `NotReady` status during a cluster update.
* You have access to the target cluster with cluster-admin privileges.

.Procedure

. Identify `NotReady` nodes by running the following command:
+
[source,terminal]
----
$ oc get nodes | grep NotReady
----

. Check node conditions by running the following command:
+
[source,terminal]
----
$ oc describe node <node_name> | grep -A 10 Conditions
----

. Check kubelet logs by running the following command:
+
[source,terminal]
----
$ oc debug node/<node_name> -- chroot /host journalctl -u kubelet -n 100
----
