Issues, Solutions and Workaround

Check portal log and found MUSIC spit error message on accessing database. On Cassandra container see disk full message in log. Go to check Rancher node filesystem "df -h", and look at /dockerdata-nfs entry to see if it's 100%. If so, clear some file under /dockerdata-nfs/dev-log/. Then restart portal-cassandra and portal-db containers by deleting them and let Helm restart new ones.

demo-k8s.sh onap init fails to populate customer data in A&AI

GLOBAL_AAI_USERNAME and GLOBAL_AAI_PASSWORD is not correct in robot chart. Update the chart and redeploy

Restart dmaap project by deleting dmaap and make sure no pv, pvc or secret are lingering. Then deploy dmaap again.

root@onap-oom-rancher:~# helm delete dev-dmaap
release "dev-dmaap" deleted

root@onap-oom-rancher:~# kubectl -n onap delete pvc dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-0
persistentvolumeclaim "dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-0" deleted
root@onap-oom-rancher:~# kubectl -n onap get pvc|grep dmaap
dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-1 Bound dev-dmaap-dbc-pg-data1 1Gi RWO dev-dmaap-dbc-pg-data 2d
root@onap-oom-rancher:~# kubectl -n onap delete pvc dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-1
persistentvolumeclaim "dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-1" deleted
root@onap-oom-rancher:~# kubectl -n onap get secret|grep dmaap