-
Notifications
You must be signed in to change notification settings - Fork 404
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
Failing svc deploy caused by nested stack changeset limit #5614
Comments
Hi @raethlo! Apologies for the trouble π. I went ahead and tested this, and also found myself trapped in a loop:
Meaning that there is no way to delete the nested stack's change set, if the root change set happens to be in a good state. The only workaround that I can think of right now is like what you've linked, unfortunately π, to create a changeset that actually does update the nested stack. For example, you can update the
From what I tested above, because of the error |
Hey @Lou1415926 thanks for looking into this ππ» I'll try to create a change that updates the nested stack and will circle back and post if it worked or not. Curious to see if the cfn team will have a better workaround. |
@raethlo yeah let me know how it goes! I tested the workaround myself yesterday, and it was successful in my case. I've discussed the issue with the engineers from cfn, and the workaround that we reached was similar to what I suggested above. Instead of altering the |
@Lou1415926 what ended up working for us after some trial & error was adding a dynamic resource tag to the deploy. copilot svc deploy --name api --env staging --resource-tags 'release-version=main-8ed091d-7576227310' --force this unblocked the cfn and also cleaned up the built up failed changesets. I don't know how common the issue is (it seems weird to me that it wasn't reported before, so it might be caused by sth on our end) but if there is no downside to doing so, copilot could automatically tag managed resources on deploy to avoid hitting the limit. Anyways, thanks for the help ππ» |
This issue is stale because it has been open 60 days with no response activity. Remove the stale label, add a comment, or this will be closed in 14 days. |
This issue is closed due to inactivity. Feel free to reopen the issue if you have any further questions! |
Hi ππ» We're facing an issue where our copilot cli managed fargate deployment (load balanced svc) fails with:
The issue is there is a lot of "failed changesets" for the nested addon stack with status:
"The submitted information didn't contain changes. Submit different information to create a change set."
. The nested addon stack rarely has a reason to change since it just contains storage and some roles but the buildup of failed changesets causes us to hit some cfn quota limit (I think). The only pointer I have been able to find as to why it happens so far is in thisaws-cli
issue aws/aws-cli#4534.So far I have not found a way how to delete the offending changesets to unblock the release because the delete commands fail with:
Apparently as pointed out in aws/aws-cli#4534 (comment) the only way to remove the changesets is to create a change from the root stack that updates the nested resource, however I am unsure how to safely do this change so that I won't create further problems with how copilot tracks the resources.
Can you please advise on what's the best way to recover the stacks to a healthy state? Since the nested addon stack will rarely contain any changes it seems that the failed changesets will build up indefinitely, is there a way to automatically clean up the failed changesets that don't contain changes?
Thanks ππ»
The text was updated successfully, but these errors were encountered: