Skip to content

Commit 57721e7

Browse files
authored
Merge pull request #88028 from kquinn1204/TELCODOCS-1840
TELCODOCS-1840 siteConfigError created to surface more info on error …
2 parents 1cef69b + 45006ed commit 57721e7

File tree

1 file changed

+20
-7
lines changed

1 file changed

+20
-7
lines changed

modules/ztp-troubleshooting-ztp-gitops-installation-crs.adoc

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -36,18 +36,31 @@ $ oc get managedcluster
3636
+
3737
[source,terminal]
3838
----
39-
$ oc describe -n openshift-gitops application clusters
39+
$ oc get applications.argoproj.io -n openshift-gitops clusters -o yaml
4040
----
4141

42-
.. Check for the `Status.Conditions` field to view the error logs for the managed cluster. For example, setting an invalid value for `extraManifestPath:` in the `SiteConfig` CR raises the following error:
42+
.. To identify error logs for the managed cluster, inspect the `status.operationState.syncResult.resources` field. For example, if an invalid value is assigned to the `extraManifestPath` in the `SiteConfig` CR, an error similar to the following is generated:
4343
+
4444
[source,text]
4545
----
46-
Status:
47-
Conditions:
48-
Last Transition Time: 2021-11-26T17:21:39Z
49-
Message: rpc error: code = Unknown desc = `kustomize build /tmp/https___git.com/ran-sites/siteconfigs/ --enable-alpha-plugins` failed exit status 1: 2021/11/26 17:21:40 Error could not create extra-manifest ranSite1.extra-manifest3 stat extra-manifest3: no such file or directory 2021/11/26 17:21:40 Error: could not build the entire SiteConfig defined by /tmp/kust-plugin-config-913473579: stat extra-manifest3: no such file or directory Error: failure in plugin configured via /tmp/kust-plugin-config-913473579; exit status 1: exit status 1
50-
Type: ComparisonError
46+
syncResult:
47+
resources:
48+
- group: ran.openshift.io
49+
kind: SiteConfig
50+
message: The Kubernetes API could not find ran.openshift.io/SiteConfig for
51+
requested resource spoke-sno/spoke-sno. Make sure the "SiteConfig" CRD is
52+
installed on the destination cluster
53+
----
54+
55+
.. To see a more detailed `SiteConfig` error, complete the following steps:
56+
57+
... In the Argo CD dashboard, click the *SiteConfig* resource that Argo CD is trying to sync.
58+
59+
... Check the *DESIRED MANIFEST* tab to find the `siteConfigError` field.
60+
+
61+
[source,text]
62+
----
63+
siteConfigError: >- Error: could not build the entire SiteConfig defined by /tmp/kust-plugin-config-1081291903: stat sno-extra-manifest: no such file or directory
5164
----
5265

5366
.. Check the `Status.Sync` field. If there are log errors, the `Status.Sync` field could indicate an `Unknown` error:

0 commit comments

Comments
 (0)