Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack is in ROLLBACK_COMPLETE state and can not be updated #107

Open
0xAJX opened this issue Jul 30, 2023 · 2 comments
Open

Stack is in ROLLBACK_COMPLETE state and can not be updated #107

0xAJX opened this issue Jul 30, 2023 · 2 comments

Comments

@0xAJX
Copy link

0xAJX commented Jul 30, 2023

Can a solution be implemented so that when this error happens, the stack is deleted and recreated?

@0xAJX 0xAJX changed the title Stack is in ROLLBACK_COMPLETE state and can not be updated. Stack is in ROLLBACK_COMPLETE state and can not be updated Jul 30, 2023
@Hanskrogh
Copy link

Any updates on this?

@SanariSan
Copy link
Contributor

SanariSan commented Feb 16, 2024

When a stack is in ROLLBACK_COMPLETE, you can actually fix it by manually updating to the last successful template through the AWS console. Although there was a suggestion about deleting and recreating the stack, AWS allows for a simpler approach by just rolling back to a stable version, which naturally avoids deletion since rollback handles that part.

Adding an auto-reset feature to the GitHub action for these situations could really simplify the process. Incorporating an option to auto-redeploy with the latest stable template when hitting certain conditions could make the whole process smoother.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants