// 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-preparing_{context}"]
= Diagnosing a ClusterGroupUpgrade CR stuck in Preparing state

[role="_abstract"]
If a `ClusterGroupUpgrade` custom resource (CR) is stuck in the `Preparing` state, the issue is typically related to policy compliance, cluster readiness, or blocking custom resources.

.Prerequisites

* You have a `ClusterGroupUpgrade` CR that is stuck in `Preparing` state.
* You have access to the {rh-rhacm-first} hub cluster with cluster-admin privileges.

.Procedure

. Check the `ClusterGroupUpgrade` status by running the following command:
+
[source,terminal]
----
$ oc get cgu <cgu_name> -n <namespace> -o yaml
----
+
Look for error messages in the `status.conditions` section.
Common causes include managed policies that do not exist or are not bound to target clusters, target clusters that are not in a ready state, and blocking custom resources that are not ready.

. Check policy compliance in {rh-rhacm} by running the following command:
+
[source,terminal]
----
$ oc get policy <policy_name> -n <namespace>
----

. Check policy details for noncompliant policies by running the following command:
+
[source,terminal]
----
$ oc describe policy <policy_name> -n <namespace>
----
+
Resolve policy compliance issues before the `ClusterGroupUpgrade` CR can proceed.
