[JIRA] [ec2-plugin] (JENKINS-29964) EC2 plugin floods AWS with API calls if it references a deleted AMI

[gamma3@cartersanders.com (JIRA)]

Carter Sanders created an issue

Jenkins / JENKINS-29964 EC2 plugin floods AWS with API calls if it references a deleted AMI Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 15/Aug/15 1:44 AM Environment: Jenkins 1.609.1 Amazon EC2 plugin 1.28 Labels: ec2-plugin aws Priority: Major Reporter: Carter Sanders If an AMI referenced in a cloud is deleted but a reference to it is retained in the cloud config, following behavior is observed A build requesting the orphaned cloud's label will wait in the queue Jenkins will flood the associated amazon account with a sufficient number of API calls to trigger rate limiting on the account, effectively taking it out of service The frequency of API calls never backs off. This is a very dangerous bug, and can take down your jenkins server and every server on the same AWS account that requires activity on the AWS API. Some sort of exponential backoff would be a far better behavior. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[luisf.pollo@gmail.com (JIRA)]

Luis Pollo commented on JENKINS-29964

Re: EC2 plugin floods AWS with API calls if it references a deleted AMI I wanted to report that I ran across a very similar issue with the plugin, however upon further investigation determined that, in my case, all AMIs referenced in cloud profiles were still valid, but the plugin seems to be recurrently and indefinitely checking for EC2 instances that had either been stopped or deleted, and that had previously been configured as nodes in Jenkins.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[luisf.pollo@gmail.com (JIRA)]

Luis Pollo edited a comment on JENKINS-29964

Re: EC2 plugin floods AWS with API calls if it references a deleted AMI

If it helps anyone that lands here, I wanted to report that I ran across a very similar issue with the plugin, however upon further investigation determined that, in my case, all AMIs referenced in cloud profiles were still valid, but the plugin seems to be recurrently and indefinitely checking for EC2 instances that had either been stopped or deleted, and that had previously been configured as nodes in Jenkins.

Add Comment