EC2 plugin 1.37 fails to provision previously defined slaves

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Francis Upton
            Reporter:
            Vincent de Lagabbe
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: