Troubleshooting Issues in Installation

The following are the known issues in the installation of Cost and Asset Management:

To clean up a previously failed deployment, do the following steps:

Note: In the following commands, replace <RELEASE_NAME> with the name you gave the Cost and Asset Management deployment.
1. Run the following command to delete the failed helm release:
```
helm delete <RELEASE_NAME> --purge --tls
```
2. Run the following command to ensure that all previous artifacts are removed:
```
 kubectl delete namespace <namespace>
```
3. Check whether the required Cost and Asset Management persistent volume claims are bound to the persistent volumes:
```
 kubectl get pvc -l release=<RELEASE_NAME>
```
4. Based on whether the 'STATUS' column is in Bound state or not, run either of the following steps:
  
  a. If the 'STATUS' column for all of the Cost and Asset Management persistent volume claims are in 'Bound' state, then set the following chart parameters on the next Cost and Asset Management helm install:
```
   core-couchdb-pv0:
     persistence:
       existingClaimName: dev-core/core-couchdb-claim0
```
```
   mariadb-tmp-pv0:
     persistence:
       existingClaimName: dev-core/mariadb-tmp-claim0
```
```
   mariadb-data-pv0:
     persistence:
       existingClaimName: dev-core/mariadb-data-claim0
```
```
   mariadb-backup-pv0:
     persistence:
       existingClaimName: dev-core/mariadb-backup-claim0
```
```
   cam-rabbitmq-pv0:
     persistence:
       existingClaimName: dev-core/cam-rabbitmq-claim0
```
```
   cam-data-pv0:
     persistence:
       existingClaimName: dev-core/cam-data-claim0
```

  b. If the CAM persistent volume claims are not in the 'Bound' state, then delete the claims with the following command:

     ```
      kubectl delete pvc -l release=<RELEASE_NAME>
     ```

Cost and Asset Management Container Debugging (kubectl)

When a container is not in running state, run the following kubectl commands to describe pods and look for errors:
```
  kubectl get pods -n <namespace>  
  kubectl describe pod <podname> -n <namespace>  
  kubectl logs <podname> -n <namespace>
```
Look for events or error messages when describing the pods or persistant volumes that are not in health states. For example, CrashLoopBackoff, Pending (for a while), Init (for a while).
Run the following commands to ensure PVs are created successfully:
```
kubectl describe pv core-couchdb-pv0
kubectl describe pv mariadb-tmp-pv0
kubectl describe pv mariadb-data-pv0
kubectl describe pv cam-data-pv0
kubectl describe pv mariadb-backup-pv0
kubectl describe pv cam-rabbitmq-pv0
```
If PVs are not setup, follow PV setup steps before you install Cost and Asset Management:

Note: If the PVs are bound, then PVs must be deleted and recreated everytime Cost and Asset Management is installed.
- If the environment variable http_proxy is used on the master and you do a PPA upload on the master, then the helm-chart does not load into the repository properly. As a workaround, either do the upload from an external machine or add mycluster and mycluster.icp to the NO_PROXY variable.
- If you are getting an error " Warning FailedMount 1m (x3 over 6m) kubelet, X.XX.XX.XX Unable to mount volumes for pod "mariadb-deploy-76c9fb5cf7-6mpdv_dev-cam(d1ab1331-bc3d-11e8-ae30-00163e01f557)": timeout expired waiting for volumes to attach or mount for pod "dev-cam"/"mariadb-deploy-76c9fb5cf7-6mpdv". list of unmounted volumes=[mariadb-data mariadb-tmp]. list of unattached volumes=[mariadb-data mariadb-tmp mariadb-config default-token-mj4x9]". Then, check if the NFS Server is correctly mounted to your local system and the mount path is specified in Persistent Volume.