Issue 1: Exception in VFC catalog during e2e service instantiation.
...
Workaround: the bug is fixed in master branch, get a copy of /service/vfc/nfvo/catalog/catalog/pub/utils/toscaparser/basemodel.py and update it in vfc_catalog container.
Issue 2: Failed to create VL between VNFs in VFC due to multivim call failure
Workaround: Remove VLs from vEPC and vIMS service design.
Issue 3: Update SDC URL in vfc_catalog container configuration file /service/vfc/nfvo/catalog/catalog/pub/config/config.py
| Code Block |
|---|
# [sdc config] SDC_BASE_URL = "http://10.0.14.1:80/api" SDC_USER = "aai" SDC_PASSWD = "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" |
Issue 4: Update aai URL in vfc_nslcm container config file /service/vfc/nfvo/lcm/lcm/pub/config/config.py
| Code Block |
|---|
# [aai config] AAI_BASE_URL = "http://10.0.14.1/aai/v11" AAI_USER = "AAI" AAI_PASSWD = "AAI" REPORT_TO_AAI = True |
Issue 5: After ONAP installation, update testlab_mso_1 docker container file /etc/mso/config.d/topology.properties with correct MSB and SDNC ip and port. Every time SO VM is restarted, this file needs to update again (don't restart the docker after config file update).
| Code Block |
|---|
msb-ip=10.12.5.180 msb-port=8080 sdnc-ip=10.12.5.181 sdnc-port=8282 |
Issue 6: SO query to A&AI fails due to SSL certificate issue
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@onap-aai-inst1:~# keytool -list -storetype pkcs12 -keystore /var/lib/docker/aufs/mnt/cc1b66f9070a991518d87032a3f35f7b6b548a110ad1389b0ac271b39ad325a0/opt/app/aai-resources/resources/etc/auth/aai-client-cert.p12 Enter keystore password: ***************** WARNING WARNING WARNING ***************** * The integrity of the information stored in your keystore * * has NOT been verified! In order to verify its integrity, * * you must provide your keystore password. * ***************** WARNING WARNING WARNING ***************** Keystore type: PKCS12 Keystore provider: SunJSSE Your keystore contains 1 entry aai-client-dev-cert, Jun 5, 2018, PrivateKeyEntry, |
Issue 7: SDC model distribution to A&AI fails due to the reason that aai babel docker doesn't come up. See details in
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@onap-aai-inst1:~# chmod uog+w /opt/aai/logroot/AAI-BAS root@onap-aai-inst1:~# docker restart testconfig_babel_1 |
Issue 8: SDC missing E2E Service and Network Service categories
Workaround: Manually add those two service types in SDC→Category Management under demo login
Issue 9: Exception in VF-C when get vim type from A&AI
...
Workaround: the bug is fixed in master branch, get a copy of /servicefc/nfvo/lcm/lcm/pub/msapi/extsys.py and update it in vfc_nslcm container.
Issue 10: SDC service design GUI doesn't respond
...
Workaround: the bug is fixed in master branch, get a copy of /servicefc/nfvo/lcm/lcm/ns/views.py and update it in vfc_nslcm container.
Issue-11: Exception in holmes when receive the ves-heartbeat event from Dmaap (the ves-heartbeat event is between from emsdriver and vescollector)
...
VEScollector configuration: /opt/app/VESCollector/etc/DmaapConfig.json . Change the topic to SEC_OTHER_OUTPUT.
Issue-12: huaweivnfm can't deal with vnfinstancename
https://jira.onap.org/browse/VFC-917
Issue-13: aai-search API is not defined in MSB, but used by Holmes
...
| Code Block |
|---|
>curl -X POST -H "Content-Type: application/json" -d '{"serviceName": "aai-search", "version": "v11", "url": "/aai/v11/search","protocol": "REST", "enable_ssl":"True", "lb_policy":"round-robin","nodes": [ {"ip": "10.0.1.1","port": "8443"}]}' "http://10.0.14.1:10081/api/microservices/v1/services"
|
Issue-14: SO can't find recipe for vIMS service (NullPointerException in log when searching recipe for the service)
Workaround: Recipe for resource VF type is only defined for "Generic"/"Network Service" category/subcategory in SO database. However "Network Service" subcategory is not defined in SDC Generic resource category, we need to manually add it and choose "Network Service" when creating vIMS_NS.
Issue-15: Holmes receives DMaaP event from VES, but doesn't seem to do any process from engine-management docker log file
Workaround: It seems rule-management docker needs to restart after engine-management docker restarts
Issue-16: Service model distribution fails
Solution: Try to restart DMaaP
Issue-17: AAI query fails
Solution: Check aai1 VM to see if all dockers are running. If not, try to restart docker.
Issue-18: After upgrade SDC, sdc-fe docker doesn't come up
...