The SO-SDC-Controller originally made use of a folder within a generated VF's CSAR, namely the ONBOARDED_PACKAGE, in order to confirm it was an ETSI based package.

As the method of creation has changed as per this requirement:  

This prevents the SO-SDC-Controller from onboarding the VNF Packages into the ETSI Catalog Manager. As the ETSI Catalog Manager attempts to read a specific folder in it's codebase, the folder: "Artifacts/Deployment/ONBOARD_PACKAGE" which it attempts to find in the VF's CSAR.