3 ms·

Call me when they get rid of UPDATE_ROLLBACK_FAILED until then it's practically useless. Whoever thought it was ever acceptable to leave your production stack

by fleitz 11y ago

Call me when they get rid of UPDATE_ROLLBACK_FAILED until then it's practically useless. Whoever thought it was ever acceptable to leave your production stack in state that requires deleting it is an idiot. Even if they fixed it I doubt I'd ever trust a service that ever acted like that with my production infrastructure.

andrewguenther 11y ago
It isn't gone, but you can at least recover from it now. https://blogs.aws.amazon.com/application-management/post/Tx11YT4MHFDZMK6/Continue-Rolling-Back-an-Update-for-AWS-CloudFormation-stacks-in-the-UPDATE-ROLL https://blogs.aws.amazon.com/application-management/post/Tx1...
- justinsb 11y ago
  Is that just a retry though? It sounds like the onus is still on you to fix the problem manually so that CloudFormation can complete its rollback, rather than e.g. being able to request a different desired CloudFormation state that might be reachable.
deleted 11y ago
[deleted]