Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
Jenkins 2.73.1, EC2 Plugin 1.37
Description
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.
Attachments
Issue Links
- 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
-
Further comment. I have a failing agent right now because the 'root command prefix' which I attempted to set as 'sudo' is not being saved in the configuration. It rather looks like I need to uninstall the entire thing and start over now.