1 個回答
- 最新
- 最多得票
- 最多評論
0
Hello,
There are several reasons a nested stack could be stuck in an UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS state. These are;
-
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.
For troubleshooting steps, see our detailed knowledge center article Why is my CloudFormation stack stuck in the UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS or UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state?
For further assistance and because it would require details that are non-public information, please open a support case with AWS using the following link
已回答 2 年前
相關內容
- 已提問 6 個月前
- 已提問 6 個月前