Troubleshooting ISD Argo Installation Issues
Most common issues encountered during installation are related to the incorrect parameters given in the file *-values.yaml. As the user realizes there is a mistake committed in *-values.yaml, the easy way to correct it is by following the steps as stated below:
Update the *-values.yaml (or whichever file name you are using).
Wait for the helm install to error out, it is better not to break the process
Simply re-execute the “helm upgrade –install …” using the below command:
ISD Argo Installation Issues
The following issues can occur when installing ISD Argo.
Agent pods are not connecting:
The log of the agent pod should give the exact reason why it is not connecting.
Remote ArgoCD objects are not in OEA-UI:
The agent configuration in OEA is automatic. No further configuration is required. Once the agent connects to the controller and you have accessed the OEA-UI, tail the agent's logs again. It will show error messages if it cannot fetch the data from ArgoCD. Most common cases are:
Incorrect URL
Incorrect or expired token.
Local ArgoCD objects are not in OEA-UI:
In the case of ISD-Argo Full Installation, local ArgoCD objects are not appearing. This is the case if automatic configuration fails. Do a manual configuration, following the instructions in agent-service.yaml, but the argoCD URL goes into the carina configuration. Details can be found in the oea-autoconfiguration job and script.
Cleaning up/Delete the installation
Execute the following commands to delete the entire installation from Kubernetes.
Option 1:
Issue these commands, and replace -n option with the namespace
Option 2:
Issue these commands, and replace -n option with the namespace
Note: Please note that this option does not delete the CRDs. CRDs need to be deleted manually using the below commands.
For deleting all CRDs related to argoproj, use the below command.
Last updated