...
If the deployment of any onap module fails, please go through these steps to redeploy the modules.
In this example, we demonstrate failure of dmaap, which normally occurs due to timeout issues.
Check the failed modules
perform 'helm ls' on the control node.
| Code Block |
|---|
ubuntu@onap-control-1:~$ helm ls
NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE
demo 1 Thu Jun 20 11:40:24 2019 DEPLOYED onap-4.0.0 Dublin onap
demo-aaf 1 Thu Jun 20 11:40:24 2019 DEPLOYED aaf-4.0.0 onap
demo-aai 1 Thu Jun 20 11:40:26 2019 DEPLOYED aai-4.0.0 onap
demo-cassandra 1 Thu Jun 20 11:40:34 2019 DEPLOYED cassandra-4.0.0 onap
demo-consul 1 Thu Jun 20 11:40:35 2019 DEPLOYED consul-4.0.0 onap
demo-dcaegen2 1 Thu Jun 20 11:40:37 2019 DEPLOYED dcaegen2-4.0.0 onap
demo-dmaap 1 Mon Jun 24 09:17:06 2019 FAILED dmaap-4.0.1 onap
demo-log 1 Sat Jun 22 14:28:43 2019 DEPLOYED log-4.0.0 onap
demo-mariadb-galera 1 Thu Jun 20 11:46:06 2019 DEPLOYED mariadb-galera-4.0.0 onap
demo-msb 1 Thu Jun 20 11:46:07 2019 DEPLOYED msb-4.0.0 onap
demo-oof 1 Thu Jun 20 11:46:09 2019 DEPLOYED oof-4.0.0 onap
demo-policy 1 Thu Jun 20 11:46:13 2019 DEPLOYED policy-4.0.0 onap
demo-portal 1 Thu Jun 20 11:46:15 2019 DEPLOYED portal-4.0.0 onap
demo-robot 1 Thu Jun 20 11:46:17 2019 DEPLOYED robot-4.0.0 onap
demo-sdnc 1 Thu Jun 20 11:46:19 2019 DEPLOYED sdnc-4.0.0 onap
demo-sniro-emulator 1 Thu Jun 20 11:46:22 2019 DEPLOYED sniro-emulator-4.0.0 onap
demo-so 1 Thu Jun 20 11:46:23 2019 DEPLOYED so-4.0.0 onap |
Delete the failed module
use the right release name from the name as shown in helm ls.
The below commands will delete all the pods and dependencies.
| Code Block |
|---|
helm delete demo-dmaap --purge
kubectl get persistentvolumeclaims -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete persistentvolumeclaims -n onap \1/' | bash
kubectl get persistentvolumes -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete persistentvolumes -n onap \1/' | bash
kubectl get secrets -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete secrets -n onap \1/' | bash
kubectl get clusterrolebindings -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete clusterrolebindings -n onap \1/' | bash
kubectl get jobs -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete jobs -n onap \1/' | bash
kubectl get pods -n onap | grep demo-dmaap | sed -r 's/(^[^ ]+).*/kubectl delete pods -n onap \1/' | bash
|
Delete any residue data from onap-nfs-server.
| Code Block |
|---|
cd /dockerdata-nfs/
sudo rm -r demo-dmaap/ |
Reinstall module
Reinstall the deleted module with the same release name as used in the deletion
| Code Block |
|---|
helm install --namespace onap -n demo-dmaap local/dmaap |
You can verify the deployment in a parallel terminal by checking the pods using the command
| Code Block |
|---|
kubectl get pods -n onap | grep demo-dmaap |
This shall show you the status of the upcoming pods during the deployment wait time.
Once this is deployed, you can verify using the "helm ls" command to check all the required modules are up and running.
Undeploy ONAP
For the release name 'demo' and namespace 'onap':
...