$ ./pattern.sh make validate-prereqTroubleshooting 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:
Validate the schema:
$ ./pattern.sh make validate-schemaCheck Argo CD health:
$ ./pattern.sh make argo-healthcheck
Checking Argo CD application status
All Argo CD applications run in the vp-gitops namespace:
List applications in
vp-gitops:$ oc get applications -n vp-gitopsInspect a child application that is out of sync or unhealthy:
$ oc describe application <application_name> -n vp-gitops
Use the Argo CD UI in the vp-gitops 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 CompletedReview logs for a specific pod:
$ oc logs -n <namespace> <pod_name>Known issues
The following known issues can affect pattern deployment:
openstack-secretsdisabled: The default pattern leavesopenstack-secretsdisabled because no Git path exists. Enable it only after you configure secret wiring. See Secret management for the RHOSO GitOps pattern.Upstream sync failures: Confirm that
targetRevisionand paths inoverrides/values-rhoso-gitops.yamlmatch a tag or branch that exists in openstack-k8s-operators/gitops.Operator install delays: Infrastructure Operators in
operator-dependenciessubscribe from the cluster catalog; allow time for OLM to resolveClusterServiceVersions(CSVs). Other applications retry automatically until their dependencies are satisfied.
For community support, open an issue in the pattern repository.
