- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello there,
Greetings for the day!
Note- Since we do not have the visibility into the resources, I am providing you the general guidance steps that might help in resolving the issue.
Unfortunately there is no awscli command that you can used in this scenario. By going through the information shared in the query that a resource has gone into Delete_Failed state with reason Internal Failure, your stack is now stuck in UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS state.
A CloudFormation stack gets stuck in the UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS or UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state when [1] :
-
CloudFormation is still in the process of removing old resources, or can't remove those resources due to a dependency issue.
-
Resource cleanup is paused because a sibling stack of a nested stack fails to update or roll back.
In this scenario, since the resource is failing to delete with reason INTERNAL FAILURE, we do not have much information to proceed with. The next step would be to check the AWS CloudTrail Event History and find the corresponding API which is failing. Once the failed API is identified, try to resolve the error message.
If the reason mentioned is API is also INTERNAL FAILURE then you need to check with the AWS Support on the progress of the ticket and they need to unstuck this stuck stack.
Article for Reference :
[1] https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-cleanup-stuck/
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren