// Module included in the following assemblies:
//
// * scalability_and_performance/ztp_far_edge/ztp-deploying-far-edge-sites.adoc

:_mod-docs-content-type: PROCEDURE
[id="ztp-troubleshooting-ztp-gitops-installation-crs_{context}"]
= Troubleshooting {ztp} by validating the installation CRs

[role="_abstract"]
The ArgoCD pipeline uses the `ClusterInstance` and `PolicyGenerator` or `PolicyGentemplate` custom resources (CRs) to generate the cluster configuration CRs and {rh-rhacm-first} policies. Use the following steps to troubleshoot issues that might occur during this process.

.Prerequisites

* You have installed the OpenShift CLI (`oc`).

* You have logged in to the hub cluster as a user with `cluster-admin` privileges.

.Procedure

. Check that the installation CRs were created by using the following command:
+
[source,terminal]
----
$ oc get AgentClusterInstall -n <cluster_name>
----
+
If no object is returned, use the following steps to troubleshoot the ArgoCD pipeline flow from `ClusterInstance` files to the installation CRs.

. Verify that the `ManagedCluster` CR was generated using the `ClusterInstance` CR on the hub cluster:
+
[source,terminal]
----
$ oc get managedcluster
----

. If the `ManagedCluster` is missing, check if the `clusters` application failed to synchronize the files from the Git repository to the hub cluster:
+
[source,terminal]
----
$ oc get applications.argoproj.io -n openshift-gitops clusters -o yaml
----
