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

EC2 plugin incorrectly reports current instance count

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • ec2-plugin
    • AWS Hosted CentOS release 6.4 (Final) x86_64
      Jenkins ver. 1.533
      Amazon EC2 plugin 1.18

      This issue has come up in the past ~48 hours or so after a dev added a theme plugin and updated plugins.

      Ec2 plugin now states that instance cap has been reached and will not provision any further instances.

      Currently no slave instances exist (all terminated several hours ago).
      Plugin has been disabled and re-enabled.
      Cloud config removed and re-created.
      Cap has been increased to 50 (normally 10)
      All without success.

      Log output as below

      02/10/2013 9:48:03 PM hudson.plugins.ec2.EC2Cloud addProvisionedSlave
      INFO: Total instance cap of 10 reached, not provisioning.
      02/10/2013 9:48:13 PM hudson.plugins.ec2.EC2Cloud addProvisionedSlave
      INFO: Total instance cap of 50 reached, not provisioning.

        1. Jenkins-Sysinfo.rtf
          109 kB
          Simon Beckett

            francisu Francis Upton
            simonbeckett Simon Beckett
            Votes:
            4 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: