[JIRA] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count

[da...@walend.net (JIRA)]

David Walend commented on JENKINS-19845 EC2 plugin incorrectly reports current instance count I've got similar symptoms, but not exactly the same. Everything was fine up until about a month ago. I didn't originally set a cap, tried setting the cap to 5, (with only the Jenkins server and one other machine are running in this account). No machine is starting when I start a new build (but the new job is queued). I get the log I've pasted below. I upgraded everything. No luck. Any thoughts? Thanks, Dave May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning. May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.