-
Bug
-
Resolution: Fixed
-
Critical
-
None
Upgraded to just released ec2-plugin 1.30. Have no Jenkins slave running. Trying to get it to auto-create a new slave by running a job.
Get this repeatedly in my jenkins log:
```
Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible
Cannot provision - no capacity for instances: -177
Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provision
Attempting provision - finished, excess workload: 1
Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible
Cannot provision - no capacity for instances: -177
Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provision
Attempting provision - finished, excess workload: 1
```
In our EC2 region, at the moment we have no Jenkins slaves running, neither on-demand nor spot. There are about 183 instances running or stopped. I think it's counting every single instance, and counting them all against the max slave.
This happens regardless of whether I have jenkins configured to create on demand slave or spot slaves.
Have to downgrade to get it to autocreate slaves.
Code changed in jenkins
User: Francis Upton IV
Path:
src/main/java/hudson/plugins/ec2/EC2Cloud.java
http://jenkins-ci.org/commit/ec2-plugin/f95e3d52c3872f0fddb1d97f23253b5593eeb641
Log:
JENKINS-32584ec2-plugin counts every instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap