Monitor the deployment

After you create the custom resource, the automation orchestrator operator validates your configuration, verifies that the required Secrets exist, runs database migrations, and deploys all application components.

Overview
Copy link

The automation orchestrator operator runs database migrations automatically before deploying the application. If you see a startup error, check the migration Job status and logs before investigating further:

$ oc get jobs -n automation-orchestrator

Check resource status with aapctl
Copy link

Important
aapctl is a Technology Preview feature. Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. Technology Preview features are not fully supported under Red Hat production SLA and may not be functionally complete. Red Hat does not recommend using Technology Preview features in production. For more information, see Technology Preview Features Support Scope in the Additional resources section.

If you installed with aapctl, use aapctl status to verify that every resource is deployed and ready. The command accepts the same --config and --set flags as install, so it checks the correct namespaces:

$ aapctl status ao
$ aapctl status aap-with-ao
$ aapctl status aap

Each resource is printed with a readiness indicator:

  Namespace/automation-orchestrator
  OperatorGroup/automation-orchestrator-operator     (automation-orchestrator)
  Subscription/automation-orchestrator-operator       (automation-orchestrator)  csv: ao-operator.v0.1.0
  AutomationOrchestrator/automation-orchestrator      (automation-orchestrator)

The command exits 0 if all resources are ready, or 1 if any are not.

If you used namespace overrides during installation, pass the same overrides:

$ aapctl status aap-with-ao --config my-config.yaml
$ aapctl status aap --set aap-operator.namespace=my-aap

Check status conditions
Copy link

From the web console:

Navigate to Operators > Installed Operators > Automation Orchestrator > AutomationOrchestrator, then click the name of the instance you created.

From the CLI:

$ oc get automationorchestrator my-orchestrator -n automation-orchestrator \
    -o jsonpath='{.status.conditions}' | jq .

Verify that the conditions show the following values:

Table 1. Expected status conditions
Condition Expected status Meaning
ConfigurationValid True The custom resource passes validation
TLSReady True Internal mTLS certificates are provisioned and valid
Progressing False Deployment is complete
Degraded False No component failures
Ready True All components are running and healthy

Verify that all pods are running
Copy link

$ oc get pods -n automation-orchestrator

You should see pods for the following components:

  • Automation orchestrator backend
  • Automation orchestrator UI
  • Automation orchestrator workflow workers
  • Automation orchestrator background worker
  • Temporal Server
  • Redis

Check per-component status
Copy link

$ oc get automationorchestrator my-orchestrator -n automation-orchestrator \
    -o jsonpath='{.status.componentStatuses}' | jq .

Access the web interface
Copy link

Open https://<your-configured-host> in a browser to access the automation orchestrator web interface. To retrieve the initial administrator password, see Retrieve the initial admin password.

Note
If you redeployed after a failed installation and cannot log in, see Redeploy over an existing database.