Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Issue 1: Exception in VFC catalog during e2e service instantiation. 

Error in vfc_catalog runtime_catalog.log
2018-02-07 18:32:39,533:[catalog.packages.ns_package]:[ns_package.py]-[100] [ERROR]:Traceback (most recent call last):
  File "/service/vfc/nfvo/catalog/catalog/packages/ns_package.py", line 96, in parse_nsd
    ret = {"model": toscaparser.parse_nsd(csar_path, inputs)}
  File "/service/vfc/nfvo/catalog/catalog/pub/utils/toscaparser/__init__.py", line 22, in parse_nsd
    tosca_obj = EtsiNsdInfoModel(path, input_parameters)
  File "/service/vfc/nfvo/catalog/catalog/pub/utils/toscaparser/nsdmodel.py", line 23, in __init__
    tosca = self.buildToscaTemplate(path, params)
  File "/service/vfc/nfvo/catalog/catalog/pub/utils/toscaparser/basemodel.py", line 39, in buildToscaTemplate
    valid_params = self._validate_input_params(file_name, params)
  File "/service/vfc/nfvo/catalog/catalog/pub/utils/toscaparser/basemodel.py", line 52, in _validate_input_params
    for key, value in params.items():
AttributeError: 'list' object has no attribute 'items'

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

# [sdc config]
SDC_BASE_URL = "http://10.0.14.1:80/api"
SDC_USER = "aai"
SDC_PASSWD = "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U"


Issue 4: Update aai URL in /service/vfc/nfvo/lcm/lcm/pub/config/config.py of vfc_nslcm container

# [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 so docker container 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).


  • No labels