Troubleshooting Binding Support Function

5 Troubleshooting Binding Support Function

This section provides information to troubleshoot the common errors that may occur during the installation and upgrade of Binding Support Function.

If helm install command Fails

This section covers the reasons and troubleshooting procedures if the helm install command fails.

Reasons for helm install failure:

Chart syntax issue [This issue could be shown in the few seconds]
Please resolve the chart specific things and rerun the helm install command, because in this case, no hooks should have begun.
Most possible reason [TIMEOUT]
If any job is stuck in a pending/error state and not able to execute, it will result in the timeout after 5 minutes as default timeout for helm command is "5 minutes". In this case, follow the below steps to troubleshoot.
helm install command failed in case of duplicated chart
```
helm install /home/cloud-user/bsf_1.5.0/sprint3.1/ocbsf-1.5.0-sprint.3.1.tgz --name ocbsf2 --namespace ocbsf2 -f cust-ashish.yaml
Error: release ocbsf2 failed: configmaps "perfinfo-config-ocbsf2" already exists
```
Here, configmap 'perfinfo-config-ocbsf2' exists multiple times, while creating Kubernetes objects after pre-upgrade hooks, this will be failed. In this case also follow the below given troubleshooting steps.
Troubleshooting steps:
1. Run the following command to cleanup the databases created by the helm install command :
```
DROP DATABASE IF EXISTS `ocpm_config_server_1_5`;
DROP DATABASE IF EXISTS `ocpm_bsf_1_5`;
DROP DATABASE IF EXISTS `bsf_release_1_5`;
```
2. Run the following command to get kubernetes objects:
```
kubectl get all -n <release_namespace>
```
  This gives a detailed overview of which objects are stuck or in a failed state.
3. Run the following command to delete all kubernetes objects:
```
kubectl delete all --all -n <release_namespace>
kubectl delete cm --all -n <release_namespace>
```
4. Execute the below command :
```
helm ls --all
```
  If this is in a failed state, please purge the namespace using the command
```
helm delete --purge <release_namespace>
```
  Note:
  If the execution of this command is taking more time, run the below command parallelly in another session to clear all the delete jobs.
```
while true; do kubectl delete jobs --all -n <release_namespace>; sleep 5;done
```
  Monitor the below command:
```
helm delete --purge <release_namespace>
```
  Once that is succeeded, press "ctrl+c" to stop the above script.
5. After the database cleanup, run the helm install command.