...
Set up ONAP and health check
| Number | Issues | JIRA | Workaround | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | SDNC fails health check intermittently |
| Reduce replica from 3 to 1 and not using clustering make the problem go away | ||||||||
2 | SDC GUI doesn't come up |
| The workaround is find an old working image for sdc-frontend and replace the failing one | ||||||||
| 3 | SO fails on health check due to bpmn can't start |
| Find a older working bpmn image from nexus3 repo and replace image version in Helm deployment with kubectl edit command | ||||||||
| 4 | Portal GUI doesn't work on 8989 port | Use Firefox with portal 30225, and when switching to SDC click on the info icon at the url bar and accept unsecure access to SDC GUI | |||||||||
| 5 | All health check failed, due to the connection failure in k8s. All cluster nodes are in Ready state: root@oom-rancher:~/oom/kubernetes/robot# kubectl -n onap get node | Restart oom-orch node can make k8s correction problem go away. You may have to restart a few pod manually like aaf-locate and aaf-service. But ONAP data seems preserved. |
VNF onboarding, service creation and distribution
...