Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47130

EC2 plugin 1.37 fails to provision previously defined slaves

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • ec2-plugin
    • 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.

            francisu Francis Upton
            vineus Vincent de Lagabbe
            Votes:
            3 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: