CloudFormation waitfor stackUpdateComplete failing when update completes
See original GitHub issueI am using AWS SDK for JavaScript version 2.200, and as of 7 days ago, the call worked fine. Now it fails in about 30 seconds following invocation. I updated to 2.334, and the stack update runs and completes after about 2 minutes. Then the waitfor fails as the stack completes. I am not using any non default timeouts or delays.
Command that is failing:
CF.waitFor('stackUpdateComplete', {StackName: existingStackId})
Error message:
{
"errorMessage": "Resource is not in the state stackUpdateComplete",
"errorType": "Error"
}
The stack does indeed complete successfully, and is in the state UPDATE_COMPLETE
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
stack-update-complete — AWS CLI 1.27.37 Command ...
Wait until stack status is UPDATE_COMPLETE. It will poll every 30 seconds until a successful state has been reached. This will exit with...
Read more >How to wait until an AWS CloudFormation stack creation or ...
Wait for an existing stack update -- aws cloudformation wait stack-update-complete wait_stack_create() { STACK_NAME=$1 echo "Waiting for ...
Read more >stack-update-complete — AWS CLI 2.9.6 Command Reference
Wait until stack status is UPDATE_COMPLETE. It will poll every 30 seconds until a successful state has been reached. This will exit with...
Read more >Stack is in state and can not be updated - Seed.run
In this state, the stack has been updated and is usable, but CloudFormation is still deleting the old resources. You need to wait...
Read more >AWS CloudFormation Stack Failure Options - YouTube
In this video, you'll see how to use AWS CloudFormation stack failure options. With this feature, you can preserve the state of provisioned ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As it’s no longer failing, I’m going to close out this issue. If you see this crop back up in a reliable way, let us know and we’ll be happy to re-open.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.