1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello,
Generally, a CloudFormation stack gets stuck in the UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS state when CloudFormation is still in the process of removing old resources, or can't remove those resources due to a dependency issue.
In most cases, CloudFormation wait for resources to delete until it reaches to resource stabilization time before its timeout. Once it will be timed out, stack should move to UPDATE_ROLLBACK_COMPLETE.
You can also refer to KC article for some more information and resolutions.
Hope above was useful to resolve to the issue.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa