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.

          [JENKINS-47130] EC2 plugin 1.37 fails to provision previously defined slaves

          Vincent de Lagabbe created issue -
          marc young made changes -
          Link New: This issue is related to JENKINS-46963 [ JENKINS-46963 ]
          marc young made changes -
          Link New: This issue is related to JENKINS-46869 [ JENKINS-46869 ]
          marc young made changes -
          Link Original: This issue is related to JENKINS-46963 [ JENKINS-46963 ]
          Alicia Doblas made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Luigi Tagliamonte made changes -
          Rank New: Ranked higher
          marc young made changes -
          Link New: This issue is related to JENKINS-47331 [ JENKINS-47331 ]
          Francis Upton made changes -
          Summary Original: EC2 plugin 1.37 does not start stopped instances when provisionning New: EC2 plugin 1.37 fails to provision previously defined slaves
          Francis Upton made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Closed [ 6 ]

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

              Created:
              Updated:
              Resolved: