|
| 1 | +--- |
| 2 | +title: Troubleshooting |
| 3 | +weight: 40 |
| 4 | +aliases: /rhoso-gitops/troubleshooting/ |
| 5 | +--- |
| 6 | + |
| 7 | +:toc: |
| 8 | +:imagesdir: /images |
| 9 | +:_content-type: ASSEMBLY |
| 10 | +include::modules/comm-attributes.adoc[] |
| 11 | + |
| 12 | +[id="troubleshooting-rhoso-gitops"] |
| 13 | += Troubleshooting the {rhoso-gitops-pattern} |
| 14 | + |
| 15 | +[id="rhoso-gitops-validate-pattern"] |
| 16 | +== Validating the pattern |
| 17 | + |
| 18 | +Run pattern validation commands from the pattern repository root: |
| 19 | + |
| 20 | +[source,terminal] |
| 21 | +---- |
| 22 | +$ ./pattern.sh make validate-prereq |
| 23 | +$ ./pattern.sh make validate-schema |
| 24 | +$ ./pattern.sh make argo-healthcheck |
| 25 | +---- |
| 26 | + |
| 27 | +[id="rhoso-gitops-check-argocd"] |
| 28 | +== Checking Argo CD application status |
| 29 | + |
| 30 | +The pattern uses two Argo CD namespaces. List applications in each: |
| 31 | + |
| 32 | +[source,terminal] |
| 33 | +---- |
| 34 | +$ oc get applications -n vp-gitops |
| 35 | +$ oc get applications -n openshift-gitops |
| 36 | +---- |
| 37 | + |
| 38 | +Inspect a child application that is out of sync or unhealthy: |
| 39 | + |
| 40 | +[source,terminal] |
| 41 | +---- |
| 42 | +$ oc describe application <application-name> -n openshift-gitops |
| 43 | +---- |
| 44 | + |
| 45 | +Use the Argo CD UI in the `openshift-gitops` namespace to review sync waves, |
| 46 | +resource health, and diff details for upstream overlays. |
| 47 | + |
| 48 | +[id="rhoso-gitops-check-pods"] |
| 49 | +== Checking pod status |
| 50 | + |
| 51 | +To verify that workloads deployed successfully, list pods that are not Running or |
| 52 | +Completed: |
| 53 | + |
| 54 | +[source,terminal] |
| 55 | +---- |
| 56 | +$ oc get pods -A | grep -v Running | grep -v Completed |
| 57 | +---- |
| 58 | + |
| 59 | +Review logs for a specific pod: |
| 60 | + |
| 61 | +[source,terminal] |
| 62 | +---- |
| 63 | +$ oc logs -n <namespace> <pod-name> |
| 64 | +---- |
| 65 | + |
| 66 | +[id="rhoso-gitops-known-issues"] |
| 67 | +== Known issues |
| 68 | + |
| 69 | +* *`openstack-secrets` disabled* — The default pattern leaves |
| 70 | + `openstack-secrets` disabled because no Git path is configured (`path: TODO`). |
| 71 | + Enable it only after you configure secret wiring and a bootstrap credential |
| 72 | + out of band. See link:../configuration/#rhoso-gitops-secret-zero[Secret zero |
| 73 | + (bootstrap credential)]. |
| 74 | +* *Upstream sync failures* — Confirm `targetRevision` and paths in |
| 75 | + `overrides/values-rhoso-gitops.yaml` match a tag or branch that exists in |
| 76 | + link:https://github.com/openstack-k8s-operators/gitops[openstack-k8s-operators/gitops]. |
| 77 | +* *Operator install delays* — Infrastructure operators in `operator-dependencies` |
| 78 | + subscribe from the cluster catalog; allow time for OLM to resolve CSVs before |
| 79 | + later sync waves run. |
| 80 | + |
| 81 | +For community support, open an issue in the |
| 82 | +link:https://github.com/cjeanner/pattern-rhoso-gitops/issues[pattern repository]. |
| 83 | + |
| 84 | +[id="next-steps_rhoso-gitops-troubleshooting"] |
| 85 | +== Next steps |
| 86 | + |
| 87 | +* link:../getting-started/[Getting started] |
| 88 | +* link:../configuration/[Configuration] |
0 commit comments