vCPE Integration Test Case
Reference
ONAP Beijing: Understanding the vFWCL use-case mechanism
Tutorial_vIMS : SDNC Updates
vCPE SO to SDNC Message Flow
Configuring SNIRO Emulator for vCPE Testing
ONAP Sanity Check
Set up ONAP and health check
Number | Issues | JIRA | Workaround |
---|
1 | SDNC fails health check intermittently | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-482 |
---|
|
| Reduce replica from 3 to 1 and not using clustering make the problem go away |
2 | SDC GUI doesn't come up | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1839 |
---|
|
| 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 | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1166 |
---|
|
| 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 NAME STATUS ROLES AGE VERSION oom-etcd-1 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1 oom-etcd-2 NotReady,SchedulingDisabled <none> 5d v1.11.2-rancher1 oom-etcd-3 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1 oom-k8s-01 Ready <none> 5d v1.11.2-rancher1 oom-k8s-02 Ready <none> 5d v1.11.2-rancher1 oom-k8s-03 Ready <none> 5d v1.11.2-rancher1 oom-k8s-04 Ready <none> 5d v1.11.2-rancher1 oom-k8s-05 Ready <none> 5d v1.11.2-rancher1 oom-k8s-06 Ready <none> 5d v1.11.2-rancher1 oom-k8s-07 Ready <none> 5d v1.11.2-rancher1 oom-k8s-08 Ready <none> 5d v1.11.2-rancher1 oom-k8s-09 Ready <none> 5d v1.11.2-rancher1 oom-k8s-10 Ready <none> 5d v1.11.2-rancher1 oom-k8s-11 Ready <none> 5d v1.11.2-rancher1 oom-k8s-12 Ready <none> 5d v1.11.2-rancher1 oom-orch-1 NotReady,SchedulingDisabled <none> 5d v1.11.2-rancher1 oom-orch-2 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1
|
| 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
Number | Issue Description | JIRA | Workaround |
---|
1 | AAI model loader fails model distribution. It appears AAI widgets are not loaded after initialization. The model loader error log shows 404 Not Found error like: 2018-11-01T22:39:25.117Z|5d569c28-6e2b-410f-98f2-17d11e978f5d|pool-2-thread-10|ModelLoader|Event-Bus|AAIRESTClient||INFO|AC0004I|AC0004I request at url = https://aai.onap:8443/aai/v14/service-design-and-creation/models/model/bb540550-d449-4745-b769-18f66508c56e resulted in http response: 404 Not Found|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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 |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-472 |
---|
|
| Bounce ueb-listener can resolve the issue |
3 | Model distribution fails on SO due to missing table entry for Generic NeutronNet | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1184 |
---|
|
| Code Block |
---|
title | sql to insert data |
---|
collapse | true |
---|
| INSERT INTO catalogdb.heat_template(`ARTIFACT_UUID`, `NAME`, `VERSION`, `BODY`, `TIMEOUT_MINUTES`, `DESCRIPTION`, `CREATION_TIMESTAMP`, `ARTIFACT_CHECKSUM`) VALUES('efee1d84-b8ec-11e7-abc4-cec278b6b50a', 'Generic NeutronNet', '1',
'heat_template_version: 2013-05-23
description: A simple Neutron network
parameters:
network_name:
type: string
description: Name of the Neutron Network
default: ONAP-NW1
shared:
type: boolean
description: Shared amongst tenants
default: True
outputs:
network_id:
description: Openstack network identifier
value: { get_resource: network }
resources:
network:
type: OS::Neutron::Net
properties:
name: { get_param: network_name }
shared: { get_param: shared }
', 10, 'Generic Neutron Template', NOW(), 'MANUAL RECORD');
INSERT INTO catalogdb.heat_template_params(`HEAT_TEMPLATE_ARTIFACT_UUID`, `PARAM_NAME`, `IS_REQUIRED`, `PARAM_TYPE`, `PARAM_ALIAS`) VALUES('efee1d84-b8ec-11e7-abc4-cec278b6b50a', 'shared', 0, 'string', NULL);
INSERT INTO catalogdb.temp_network_heat_template_lookup (`NETWORK_RESOURCE_MODEL_NAME`, `HEAT_TEMPLATE_ARTIFACT_UUID`,`AIC_VERSION_MIN` , `AIC_VERSION_MAX` ) VALUES ('Generic NeutronNet','efee1d84-b8ec-11e7-abc4-cec278b6b50a','2.0','2.5'); |
If table is populated with wrong content (e.g. Generic NetronNet yaml), you can run SQL command to update it Code Block |
---|
root@mariadb:/# cat neutron.sh
mysql -uroot -ppassword -e 'update catalogdb.heat_template set body="
heat_template_version: 2013-05-23
description: A simple Neutron network
parameters:
network_name:
type: string
description: Name of the Neutron Network
default: ONAP-NW1
shared:
type: boolean
description: Shared amongst tenants
default: False
outputs:
network_id:
description: Openstack network identifier
value: { get_resource: network }
resources:
network:
type: OS::Neutron::Net
properties:
name: { get_param: network_name }
shared: { get_param: shared }" where name="Generic NeutronNet"' |
|
4 |
| |
|
Service Instantiation
Number | Issue | JIRA | Workaround |
---|
1 | Failed to create vCPE customer service with error message in bpmn log asCannot orchestrate Service-Macro-Create without user params with a vnf | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1189 |
---|
|
|
|
2 | DHCP_MAP is not populated in SDNC because kea DHCP is not downloaded correctly | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-712 |
---|
|
| You can manually download kea lib. See vCPE tutorial |
3 | CloudOwner is not defined in SDNC configuration. vCPE customer service instantiation will fail | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-448 |
---|
|
| Add cloud-region.cloud-owner=CloudOwner container sdnc-sdnc-0: /opt/sdnc/data/properties/generic-resource-api-dg.properties |
4 | Customer service instantiation uses self-service flow and failed to find cloud owner | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-511 |
---|
|
| Add preload to GRA for the vBRG based on SO name to be assigned zRegionOne1base_vgw_0 , zRegionOne2base_vgw_0, etc. |
5 | SUBCATEGORY and ALLOTTED_RESOURCE_ROLE not set in allotted_resource_customization/allotted_resource tables correctly |
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-1909 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1200 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1208 |
---|
|
| Manually update the allotted_resource table and allotted_resource_customization tables to set TunellXCon and BRG |
6 | mso.workflow.sdnc.replication.delay not set in override.yaml for BPMN | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1198 |
---|
|
| Manually set it to PT60S |
7 | SO query to AAI after SDNC service-topology-operation fails - arUrl is null | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1201 |
---|
|
| Need patch |
|
|
|
|