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

EC2 plugin fails to honour instance cap of 1

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Component/s: ec2-plugin
    • Labels:
    • Environment:
      Jenkins 2.89.2 (latest Docker), with latest plugins - ec2-plugin 1.38
    • Similar Issues:

      Description

      With a basic EC2 configuration of any AMI, if you set either or both the global instance cap and the AMI instance cap to 1, it will launch up to 2 nodes instead. If you omit a value from either, and rely on a cap only on the AMI or the global state, then the same occurs. 

      This happens on 1.38 and 1.36. I haven't tested other versions.

      This potentially affects instances that you rely on stopping instead of terminating, and also affects machines that rely on uniqueness, such as Active Directory joined clients.

        Attachments

          Activity

          Hide
          thoulen FABRIZIO MANFREDI added a comment -

          Seems the last version 1.45 is not affacted

          Show
          thoulen FABRIZIO MANFREDI added a comment - Seems the last version 1.45 is not affacted

            People

            Assignee:
            francisu Francis Upton
            Reporter:
            kylegordon Kyle Gordon
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: