- 최신
- 최다 투표
- 가장 많은 댓글
I understand that root stack is stuck with UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS, which is very common behavior in case of nested stack where some conflicts happen and one of the most common reason is, if updates were pushed directly to child stack.
I assume you don't have AWS support, so I'd suggest you to wait for an hour and let cloudformation timeout, once it times out, you should be able to do "Continue Rollback"
Also, you can try this, if it helps(very less likely):
aws cloudformation continue-update-rollback --stack-name <Root_Stack> --resources-to-skip <Child_Stack> --profile <CLI_Profile>
Please refer Cloudformation Update Stacks, specifically "Cancelling a stack update", "Prevent updates to stack resources", "Continue rolling back an update"
Also take a look at this re:Post
PS: AWS support is very much of help in such scenarios as they do take care of things from their end for faster resolution. If you have support plan and can create Technical case, please log a case following the instructions from here.
Hope you find this helpful.
Abhishek
관련 콘텐츠
AWS 공식업데이트됨 2년 전
It's been 2 1/2 hours since the nested stacks entered the UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS state. During the attempted update, no actions were performed due to a stack role permission issue. Based on the documentation https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-nested-stacks-are-stuck my only course of action is to contact support. However that is an expensive endeavor.
I understand, nested stacks sometime cause trouble if not handled appropriately. My response is fairly delayed here and I hope your stack would have come to UPDATE_ROLLBACK_COMPLETE state. Seems like you don't have support plan through which you can contact support, then only option is to wait and let it clear by itself as I can say that, it'd clear in sometime by itself. And if it doesn't then it's in non-recoverable state and can only be fixed by support. I've been in such situations, where I had support plan and support always helped effectively but there were cases where I was able to resolve it by myself by the mentioned command in the answer.