title	Troubleshooting
weight	40
aliases	/rhoso-gitops/troubleshooting/

Table of Contents

Troubleshooting the {rhoso-gitops-pattern}

Validating the pattern

Run pattern validation commands from the pattern repository root:

$ ./pattern.sh make validate-prereq
$ ./pattern.sh make validate-schema
$ ./pattern.sh make argo-healthcheck

The pattern uses two Argo CD namespaces. List applications in each:

$ oc get applications -n vp-gitops
$ oc get applications -n openshift-gitops

Inspect a child application that is out of sync or unhealthy:

$ oc describe application <application-name> -n openshift-gitops

Use the Argo CD UI in the openshift-gitops namespace to review sync waves, resource health, and diff details for upstream overlays.

To verify that workloads deployed successfully, list pods that are not Running or Completed:

$ oc get pods -A | grep -v Running | grep -v Completed

Review logs for a specific pod:

$ oc logs -n <namespace> <pod-name>

openstack-secrets disabled — The default pattern leaves openstack-secrets disabled because no Git path is configured (path: TODO). Enable it only after you configure secret wiring and a bootstrap credential out of band. See Secret zero (bootstrap credential).
Upstream sync failures — Confirm targetRevision and paths in overrides/values-rhoso-gitops.yaml match a tag or branch that exists in openstack-k8s-operators/gitops.
Operator install delays — Infrastructure operators in operator-dependencies subscribe from the cluster catalog; allow time for OLM to resolve CSVs before later sync waves run.

For community support, open an issue in the pattern repository.