Notifications

321 views

Description

Due to the invalid parameter CustomTags being added to the AWSCloudFormationTemplateUtil script include, AWS CFT template deployments fails with the following error in the wrapper.log file in the MID Server:

Exhausted after delivery attempt: 1 caught: java.lang.RuntimeException: Failed to execute API - Failed with status code and message: 400:

<ErrorResponse xmlns="http://cloudformation.amazonaws.com/doc/2010-05-15/">

2017/11/20 23:01:25 |  <Error>

2017/11/20 23:01:25 |    <Type>Sender</Type>

2017/11/20 23:01:25 |    <Code>ValidationError</Code>

2017/11/20 23:01:25 |    <Message>Parameters: [CustomTags] do not exist in the template</Message>

2017/11/20 23:01:25 |  </Error>

2017/11/20 23:01:25 |  <RequestId>ba3446e4-ce46-11e7-be85-47cc7720c619</RequestId>

2017/11/20 23:01:25 |</ErrorResponse>

2017/11/20 23:01:25 |  (script_include:CloudRESTAPIInvoker; line 101)

2017/11/20 23:01:25 | 

2017/11/20 23:01:25 | Message History

 

Steps to Reproduce

 

  1. Import AWS Cloud Template.

  2. Create associated Blueprint and Catalog Item.

  3. Provision the Catalog item.

    Provisioning fails.

Workaround

Comment out lines 42-47 of the AWSCloudFormationTemplateUtil script include. Note that this workaround will cause the custom tag not to be included in the template.

Comment out the following lines:
var tagParameter = {};
processedParams['CustomTags'] = tagParameter;
tagParameter.type = 'String';
tagParameter.source = 'Text';
tagParameter.mandatory = false;
tagParameter.order = order;


Related Problem: PRB1211351

Seen In

Jakarta Patch 3
Jakarta Patch 4

Fixed In

Jakarta Patch 5
Kingston

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-03-22 05:20:07
Published:2017-11-21