When using S3 storage the original csar is no longer present in the VSP csar and hence is no longer present in the VF csar. It is being replaced by a file with contains the details of how to retrieve the original csar from S3 storage.

The ETSI NSD CSAR plugin depends on the presence of the original csar to fetch the VNFD for inclusion on the ETSI NSD CSAR. 

Two possible ways to fix:

• Include the original csar (with the images stipped out in the VSP and VF CSAR as is the case when S3 not in use and add the S3 storage details in another file
• Include the VNFD seperately as an artifact in the VSP and VF CSARS and update the ETSI NSD CSAR plugin to fetch the VNFD from the new location