-
Bug
-
Resolution: Done
-
Medium
-
Dublin Release
-
None
After changed related to DCAEGEN2-855 were made; namely following changes outlined below; when deployment handler attempts to upload a blueprint to cloudify; following error is generated by Cloudify: {"status":500,"message":"Internal Server Error"}.
This bug is happening on Cloudify version 4.4.
Changes that caused the bug:
===================
in cloudify.js:
replace:
zip.addFile('work/', new Buffer(0));
zip.addFile('work/blueprint.yaml', new Buffer(blueprint, 'utf8'));
with:
zip.addFile('work/blueprint.yaml', Buffer.from(blueprint, 'utf8'));
in package.json:
replace: "adm-zip": "0.4.7",
With: "adm-zip": "0.4.13",
Error from Cloudify:
=============
2019-02-27T15:35:06.736Z|0b33a838-14ad-4af2-b2c6-91a48b4c0060|deploymentId(dcae_policy-handler-3): uploading blueprint|^
2019-02-27T15:35:06.736Z|0b33a838-14ad-4af2-b2c6-91a48b4c0060|uploadBlueprint dcae_policy-handler-3|^
2019-02-27T15:35:06.738Z|0b33a838-14ad-4af2-b2c6-91a48b4c0060|Calling https://ecompc-orcl-dev-s1.ecomp.idns.cip.att.com:443/api/v3.1/blueprints/dcae_policy-handler-3 with Tenant: default_tenant|^
2019-02-27T15:35:06.805Z|0b33a838-14ad-4af2-b2c6-91a48b4c0060|Error: {"status":500,"body":"
","json":{"status":500,"message":"Internal Server Error"}} while deploymentId(dcae_policy-handler-3): uploading blueprint|^
- relates to
-
DCAEGEN2-855 deployment handler uploadBlueprint which is not valid to cloudify (folder as file)
- Closed