-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.73.1, EC2 Plugin 1.37
With the EC2 plugin version 1.37, existing stopped instances are not started again during provisioning with the following message in the Jenkins log when the instance cap is reached:
Cannot provision - no capacity for instances: -1
reverting to version 1.36 fixes the issue.
- is related to
-
JENKINS-46869 Can not register an EC2 instance as a node agent
-
- Resolved
-
-
JENKINS-47331 1.37 slave launcher prefixing breaks installations without prefix strings.
-
- Closed
-
I just ran into this issue myself after weeks of avoiding upgrading to 1.37 (I forgot today). I went to recreate my cloud and things got messy real fast so I just changed one item (in my case switching from T2Large to T2Micro) and saved the configuration. This was enough to allow the plugin to start my agents up successfully.