-
Notifications
You must be signed in to change notification settings - Fork 76
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
Cloudformation Stack stuck in UPDATE_ROLLBACK_FAILED due to ConnectionStack resource failure #2756
Comments
Ok, a little more information as I continue to dig into this. Looking at AppSync directly, the resolvers for the Currently, my plan of attack is to rollback the cloudformation stack while skipping the problematic resources, manually recreate the |
transferring the issue to API repository for better assistance |
Hey @alex-griffiths, Thanks for raising this. Have you made any other changes to schema? Also, Could you please verify if the |
These were the only changes I made to the schema, and ‘ChannelassetResolver’ does exist in my local directory
…On Tue, Aug 13, 2024 at 4:42 am, Anil Maktala ***@***.***(mailto:On Tue, Aug 13, 2024 at 4:42 am, Anil Maktala <<a href=)> wrote:
Hey ***@***.***(https://github.com/alex-griffiths), Thanks for raising this. Have you made any other changes to schema? Also, Could you please verify if the ChannelassetResolver exist in your local directory amplify/backend/api/<apiname>/build/api/resolver?
—
Reply to this email directly, [view it on GitHub](#2756 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AEWUL7YCXK5JKMVKHBQ4CUDZRD627AVCNFSM6AAAAABMIZUDWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBUGY4DENZTHA).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
22.0.0
Amplify CLI Version
12.10.10
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I have just tried to push a change to my development environment. The change was simply adding an Auth group to an existing table.
Pushing this up resulted in my Cloudformation stack getting stuck in the
UPDATE_ROLLBACK_FAILED
state, with various nested stacks in the same state, or some variation ofUPDATE_ROLLBACK...
.The offending stack appears to be my
ConnectionStack
which failed with the status "The following resource(s) failed to update: [EFORassetResolver, ChannelassetResolver, DORItemassetResolver, DeviceEngineCycleassetResolver].". Digging into this, theChannelassetResolver
failed with a not found error:I've previously run into issues with the Cloudformation stacks, and the advice those times has usually been along the lines of, manually rollback the root resources, while skipping the problematic stack, and then fix that stack somehow because the rest of the Cloudformation stack expects it to be a certain way when it is not. I'm not prepared to go through that currently, and would instead like some help understanding first how I got into this mess before trying to make those changes.
Expected behavior
That the Cloudformation stack doesn't getting deadlocked when pushing a change
Reproduction steps
amplify push -y
Project Identifier
90ee5db58b8b8ec82b9721ec8bcea978
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: