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

ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: ec2-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      Upgraded to just released ec2-plugin 1.30. Have no Jenkins slave running. Trying to get it to auto-create a new slave by running a job.

      Get this repeatedly in my jenkins log:
      ```
      Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible
      Cannot provision - no capacity for instances: -177
      Jan 24, 2016 2:00:52 PM INFO hudson.plugins.ec2.EC2Cloud provision
      Attempting provision - finished, excess workload: 1
      Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveIfPossible
      Cannot provision - no capacity for instances: -177
      Jan 24, 2016 2:00:59 PM INFO hudson.plugins.ec2.EC2Cloud provision
      Attempting provision - finished, excess workload: 1
      ```

      In our EC2 region, at the moment we have no Jenkins slaves running, neither on-demand nor spot. There are about 183 instances running or stopped. I think it's counting every single instance, and counting them all against the max slave.

      This happens regardless of whether I have jenkins configured to create on demand slave or spot slaves.

      Have to downgrade to get it to autocreate slaves.

        Attachments

          Activity

            People

            • Assignee:
              francisu Francis Upton
              Reporter:
              mbarrien Michael Barrientos
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: