vFW distribution works but looks like SO can’t read the CSAR properly. It doesn’t look like issue with distribution itself.

details:

 

we re-run the use case and we collected the attached 5 files:

-Screenshot about distribution

-Heat template for vfmodule and vfw  

-sdnc log during distribution

-sdc-controller-so log during distribution

 

we bring to your attention the following error we noticed in both SO and SDNC logs:

 

2019-06-14T08:47:48.599Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_function is not found

2019-06-14T08:47:48.599Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_naming_code is not found

2019-06-14T08:47:48.600Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_role is not found

2019-06-14T08:47:48.600Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_type is not found

2019-06-14T08:47:48.600Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_function is not found

2019-06-14T08:47:48.601Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_naming_code is not found

2019-06-14T08:47:48.601Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_role is not found

2019-06-14T08:47:48.601Z||pool-4-thread-3|||||ERROR|||processProperties - property nf_type is not found

2019-06-14T08:47:48.687Z||pool-4-thread-3|||||ERROR|||Csar with UUID: 991025b4-5918-4b95-98d9-55a2cee23241 already exists

2019-06-14T08:48:22.335Z||pool-4-thread-3|||||ERROR|||Error updating CatalogDBStatus

 

The use case was carried out by manual onboarding and by robot (1.4.0. and 1.4.1) with the same issue.