-
Bug
-
Resolution: Done
-
Medium
-
London Release
-
None
CNFM LCM application expects the resource CSAR from SDC to be written in the following order(TOSCA.meta before asd.yaml),
TOSCA-Metadata/TOSCA.meta ... Definitions/asd.yaml ...
If the file gets written in a different order (asd.yaml before TOSCA.meta), CNFM LCM application fails to process it.
Cause:
Same ZipInputStream processed twice to get the TOSCA.meta and asd.yaml files. Once the file is read from ZipInputStream, it gets marked as read. So the same file will not be processed again in the same zipinputstream.
If the asd.yaml file exists in the stream before TOSCA.meta. It fails to read the asd.yaml as it is marked as read while reading TOSCA.meta.
Steps to Reproduce:
- Create a CSAR archive with the files in the order of
... Definitions/asd.yaml ... TOSCA-Metadata/TOSCA.meta
- Attempt to process the CSAR file using CNFM LCM application.
Expected Result:
Application should process the CSAR file independent of the CSAR file contents order.