Reference
ONAP Beijing: Understanding the vFWCL use-case mechanism
ONAP Sanity Check
Set up ONAP and health check
| Number | Issues | JIRA | Workaround |
|---|---|---|---|
| 1 | SDNC fails health check intermittently | SDNC-482 - Getting issue details... STATUS | Reduce replica from 3 to 1 and not using clustering make the problem go away |
2 | SDC GUI doesn't come up | SDC-1839 - Getting issue details... STATUS | 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 | SO-1166 - Getting issue details... STATUS | 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 |
VNF onboarding, service creation and distribution
| Number | Issue Description | JIRA | Workaround |
|---|---|---|---|
| 1 | AAI model loader fails model distribution. It appears AAI widgets are not loaded after initialization | AAI-1759 - Getting issue details... STATUS | run the script manually root@oom-rancher:~# kubectl exec -it dev-aai-aai-traversal-b95847c96-fklkx -n onap gosu aaiadmin /opt/app/aai-traversal/bin/install/updateQueryData.sh |
| 2 | Model distribution fails in SDNC because ueb-listener did not connect to SDC successful when starting | SDNC-472 - Getting issue details... STATUS | Bounce ueb-listener can resolve the issue |