// 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-cgu-failed_{context}"]
= Diagnosing a ClusterGroupUpgrade CR that failed on some clusters

[role="_abstract"]
If a `ClusterGroupUpgrade` custom resource (CR) completes but some clusters show a `failed` status, investigate the failed clusters individually to identify the root cause.

.Prerequisites

* You have a `ClusterGroupUpgrade` CR that shows failed clusters.
* You have access to the {rh-rhacm-first} hub cluster with cluster-admin privileges.

.Procedure

. Check detailed cluster status in the `ClusterGroupUpgrade` CR by running the following command:
+
[source,terminal]
----
$ oc get cgu <cgu_name> -n <namespace> -o jsonpath='{.status.clusters}'
----
+
The following example shows the output:
+
[source,json]
----
{
  "spoke1": "complete",
  "spoke2": "failed",
  "spoke3": "inprogress"
}
----

. Check {cgu-operator} logs for errors related to the failed clusters by running the following command:
+
[source,terminal]
----
$ oc logs -n openshift-operators deployment/cluster-group-upgrades-controller-manager
----

. Check policy violation events on the failed cluster by running the following command:
+
[source,terminal]
----
$ oc --context=<failed_cluster> get events -A --sort-by='.lastTimestamp' | tail -20
----
