// 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-image-pull_{context}"]
= Diagnosing image pull failures during updates

[role="_abstract"]
If image pull failures occur during an update, common causes include registry connectivity issues, images not mirrored to a disconnected registry, and image pull authentication failures.

.Prerequisites

* You have image pull failures during a cluster update.
* You have access to the target cluster with cluster-admin privileges.

.Procedure

. Check image pull status on nodes by running the following command:
+
[source,terminal]
----
$ oc get events -A --field-selector reason=Failed --sort-by='.lastTimestamp' | grep -i image
----

. For disconnected environments, verify image mirroring by running the following command:
+
[source,terminal]
----
$ oc get imagedigestmirrorset
----
+
[NOTE]
====
In {product-title} 4.13 and earlier, image mirroring was configured with `ImageContentSourcePolicy` resources. In {product-title} 4.14 and later, `ImageDigestMirrorSet` resources replace `ImageContentSourcePolicy`. If your cluster was originally installed on a version earlier than 4.14, check both resource types.
====

. Test image pull from a node by running the following command:
+
[source,terminal]
----
$ oc debug node/<node_name> -- chroot /host podman pull <image_url>
----
