-
Notifications
You must be signed in to change notification settings - Fork 44
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
Rate limit issue - DescribeChangeSet #218
Comments
Hi @richardmilnerwatts , I had it too, but i also deleted pending ChangeSets that didn't had any update. |
Interesting, I didn't have to do anything other than re-run the CodePipeline for Factory. I assume it was a temporary issue which caused the retry / rate limit to be hit. "Re-run" it is probably an acceptable solution being honest :) I'm only reporting it in case the incidence of this is higher than expected - I've never seen this before in hundreds of Factory runs. |
Btw , are you running in eu-central-1 region ? Me too, for 7 AWS Organizations , first time i see this, but i see also piled up a lot of changeset faileds ( becasue thate was no change ) - which is expected normal behavior. However i did hit another problem today , with Setuptools and Troposphere 2to3. |
I've had further recurrences of this, it looks like each time we run the full Factory pipeline it creates a Change Set in the CFN which creates the CodePipelines for each product. At some point a critical threshold of "failed" (no change) Change Sets is reached, which Factory seems to iterate through causing a rate limit to be hit. I manually deleted around 100 change sets, this is stopped the issue occuring and shaved some time of the Factory pipeline as well it seems. |
would it make sense if I disabled the use of changesets ? |
That or some mechanism to clean up FAILED change sets after we've checked to see if there are any updates to the stack(s) in question. Thanks, |
It's this feature in the aws-cli project: |
change sets with zero changes cannot be executed. I have added something to delete them in better boto and will include it in the next release: https://github.com/eamonnfaherty/better-boto/releases/tag/0.43.0 |
That was a fast change. |
There is a change in 0.68.0 that will delete changesets when there are no changes. This should avoid the issue from occurring. To clean up existing change sets you can use the following script: https://gist.github.com/eamonnfaherty/5eec7ff831adbd0eaa8e922433979fec |
I had an isolated error with an API rate limit being hit in factory. The error did not occur when I re-ran the pipeline:
The text was updated successfully, but these errors were encountered: