-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom resource deployment fails in v6.0.0 #749
Comments
Hi @bchunduri, thank you for reporting this issue. Please try following:
Additionally:
Please let us know if any questions. Thanks, |
Hi @abhirpat, thanks for the quick suggestions and let me review your points:
Thanks, Babu |
@bchunduri Thank you. Could you please try using latest template v6.0.2 and update us if you have this issue? |
@bchunduri, I deployed v6.0.0 VPC template with 26 characters in the stack name and wasn't able to replicate the issue. I was able to deploy successfully. |
Hi @michaelin-96 , thanks and have you tried stack names with more than 26 characters ? |
@abhirpat , wonder to see another minor version released in no time ! This leave us in dilemma to hold over to a stable release :( |
@bchunduri, if you create a stack name with over 26 characters for v6.0.0 then it will fail. See #741. This is addressed v6.0.1 and onwards. |
@bchunduri - thank you for bringing this to our attention. Please use the latest version to update your stack. We will look into this more and be in touch shortly. |
Hi @bchunduri |
Hi Team,
We are deploying the new version of AWS QnABot v6.0.0 using the Cloudformation stacks and it failed to create all the custom resources with error statement as shown in below example:
CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [xxxxxxx-xxxxxx-xxxxxx-xxxx]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.
There were no cloudwatch events recorded against any of the requestId's from the failed resources and the triggered lambda logs throwing this error:
"errorType": "Runtime.ImportModuleError",
"errorMessage": "Error: Cannot find module 'index'\nRequire stack:\n- /var/runtime/index.mjs",
Please investigate, review and assist us to unblock this problem. Appreciate your swift action.
The text was updated successfully, but these errors were encountered: