Issue | Solution/Workaround | JIRA |
---|---|---|
Can't login ONAP portal GUI | 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 | |
SDC model distribution fails with no downloaded or notified | 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 root@onap-oom-rancher:~# kubectl -n onap delete pvc dev-dmaap-dbc-pg-data-dev-dmaap-dbc-pg-0 root@onap-oom-rancher:~/oom/kubernetes# helm deploy dev local/onap -f /root/integration-override.yaml --namespace onap | |
Can't enter SDC GUI from Portal with error message saying SDC fe can not be connected | Check your local /etc/hosts to see if ip addresses are the latest | |
SDC model distribution doesn't show SDNC, the rest components receive the model distribution though | Check dev-sdnc-sdnc-ueb-listener container log /opt/onap/sdnc/ueb-listener/logs/ueb-listener.out to see if it has error saying failed to authenticate with SDC. If so, restart the pod by deleting the pod and let K8S start a new one. |
Page Comparison
General
Content
Integrations