vCPE Integration Test CaseTest Preparation:
ONAP Sanity Check
Set up ONAP and
...
health check
Number | Issues | JIRA | OOM installationWorkaround |
---|
Health check | SDNC fails health check intermittently | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-482 |
---|
|
| Reduce replica from 3 to 1 and not using clustering make the problem go away |
Portal and GUI | SDC GUI doesn't come up. The workaround is find an old working image for sdc-frontend and replace the failing one | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDC-1839 |
---|
|
| Model distribution | | The workaround is find an old working image for sdc-frontend and replace the failing one |
|
| |
|
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 |
.Workaround: | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-1759 |
---|
|
| 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 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
|
AAI-1759 | Bounce ueb-listener can resolve the issue |
|
|
|
|