Troubleshooting the RHOSO GitOps pattern

Validate the RHOSO GitOps pattern deployment, inspect Argo CD application and pod status, and review known issues. Use these procedures when child applications fail to sync, pods are unhealthy, or you need to confirm a successful deployment.

Validating the pattern

Run the following pattern validation commands from the pattern repository root:

Validate prerequisites:
```
$ ./pattern.sh make validate-prereq
```
Validate the schema:
```
$ ./pattern.sh make validate-schema
```
Check Argo CD health:
```
$ ./pattern.sh make argo-healthcheck
```

Checking Argo CD application status

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

List applications in vp-gitops:
```
$ oc get applications -n vp-gitops
```

List applications in rhoso-gitops-standalone:

$ oc get applications -n rhoso-gitops-standalone

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

$ oc describe application <application_name> -n rhoso-gitops-standalone

Use the Argo CD UI in the rhoso-gitops-standalone namespace to review application status, resource health, and diff details for upstream overlays.

Checking pod status

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>

Known issues

The following known issues can affect pattern deployment:

openstack-secrets disabled: The default pattern leaves openstack-secrets disabled because no Git path exists (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 that 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 ClusterServiceVersions (CSVs). Other applications retry automatically until their dependencies are satisfied.

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

Edit this page Open a documentation issue