Troubleshooting Operator Based Installer

This section describes how to troubleshoot some of the common issues you may face when installing the Release application using Operator-based installer.

Error while processing YAML document at line 1 of XL YAML file

Symptom Solution
When the deployment starts, XL CLI script fails
to run and displays the following error message:

Script Error
Restart the deployment using XL CLI.
xl apply -v -f digital-ai.yaml
Note: The above command applies the digital-ai.yaml wrapper file that bundles all other files, such as infrastructure file, environment file, and so on.

Only the Operator control manager pod gets deployed only on the Kubernetes cluster

Symptom Solution
The XL CLI script runs successfully, but only the Operator control manager pods are deployed on the Kubernetes cluster. No other pods are deployed. Clear the Operator deployment as follows and restart the deployment using XL CLI:
  1. Run the Kubectl get crd and delete the Operator corresponding to CRD:
    kubectl delete crd
  2. Go to /digital-ai/kubernetes/template path in extracted ZIP file, and run the following command:
    kubectl delete -f

Note: To troubleshoot the issue on Openshift AWS cluster, replace the kubectl command with oc.

Deployment activation fails after deleting operator

Symptom Solution
After deleting the operator customer resource definition (CRD) and the operator, the redeployment process fails to create pods when you attempt to activate the deployment process by running the following command:
xl apply -v -f digital-ai.yaml
If you do not have a local Release instance, only then use the kubectl delete -f command to remove the Release instance. If you have a local Release instance with deployment details, use the make undeploy command to remove the Operator, and retry the deployment process.

Upgrade to Operator-based solution fails

Symptom Solution
The upgrade to Operator-based solution from the Helm Charts-based solution fails.
  1. Restore the database instance.
  2. Clean the deployments. For more information, see Uninstall Release.
  3. Update the dairelease_cr.yaml file to use the external database as follows:
    1. Search for UseExistingDB parameter in the dairelease_cr.yaml file.
    2. Set Enabled parameter to True.
    3. Remove the comment tag from the following parameters:
      • XL_DB_URL

      • Troubleshoot Upgrade FailureTroubleshoot Upgrade Failure
    4. Update the external database credentials.
  4. Redeploy the Release instance.