|
||||||||
|
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.
I have two issues.
1) Changing the instance cap does not get reflected. Jenkins log continues to show the following
"INFO: Total instance cap of 5 reached, not provisioning.
Sep 16, 2014 4:40:10 AM hudson.plugins.ec2.EC2Cloud provision
INFO: Excess workload after pending Spot instances: 3"
I learned that from Matt Wise that the count might be related to the AMI. Since I have 20 instances running using the current AMI. I have created a new AMI and change the configuration to use the new AMI instead. However, it still does not launch new EC2 instance when jobs in the queue.