![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2-plugin |
|
Created:
|
25/Mar/15 8:19 PM
|
|
Description:
|
Instance counts towards the cap feature are incorrectly counted when you use the same AMI for multiple jenkins slave types it with differing ec2 instance types. The count is a sum of all the instances provisioned by the plugin rather than the number provisioned per discrete slave configuration.
https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2Cloud.java#L241
If the ami id and the tag jenkins_slave_type match, it is counted toward the cap.
Scenario:
slave description: small slave
ami: ami-12345
instance type: t1.small
cap: 5
slave description: big slave
ami: ami-12345
instance type: c3.xlarge
cap: 2
If there are five "small slaves" running it won't provision any "big slaves", reports the following:
AMI Instance cap of 2 reached for ami ami-12345, not provisioning.
|
|
Environment:
|
ec2-plugin 1.26
jenkins 1.605
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Trevor Baker
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
