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

ec2-plugin 1.42 doesn't work well with ec2 spot instances

    Details

    • Similar Issues:
    • Released As:
      1.45

      Description

      ec2-plugin 1.42 Creates a lot of spot instances and does not use it

      1.41 - works great

        Attachments

          Activity

          Hide
          stan_crofts Stan Crofts added a comment -

          I am unable to launch spot instances on 1.42. I get the following output in the log:

           

          INFO: Connecting to null on port 22, with timeout 10000.
          Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud
          INFO: Connected via SSH.
          Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud
          WARNING: Authentication failed. Trying again...
          Show
          stan_crofts Stan Crofts added a comment - I am unable to launch spot instances on 1.42. I get the following output in the log:   INFO: Connecting to null on port 22, with timeout 10000. Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud INFO: Connected via SSH. Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud WARNING: Authentication failed. Trying again...
          Hide
          thaipham Thai Pham added a comment -

          This happened to me as well. I had to compile 1.40.1 and uploaded it to my Jenkins. I didn't use 1.41 due to the deadlock issue.

          Show
          thaipham Thai Pham added a comment - This happened to me as well. I had to compile 1.40.1 and uploaded it to my Jenkins. I didn't use 1.41 due to the deadlock issue.
          Hide
          thaipham Thai Pham added a comment -

          My Jenkins version is 2.150.3, EC2 plugin is 1.42. I have 2 templates which create Ubuntu spot instances and Windows on-demand instances. The Windows instances have already been created successfully and are building jobs well. When I tried to provision a Linux spot instance from the template, for some reason, the plugin incorrectly detected the wrong IP address, which belong to a running Windows on-demand instance, even though it got the Spot Instance Request ID right because I could terminate the instance after that.

          Show
          thaipham Thai Pham added a comment - My Jenkins version is 2.150.3, EC2 plugin is 1.42. I have 2 templates which create Ubuntu spot instances and Windows on-demand instances. The Windows instances have already been created successfully and are building jobs well. When I tried to provision a Linux spot instance from the template, for some reason, the plugin incorrectly detected the wrong IP address, which belong to a running Windows on-demand instance, even though it got the Spot Instance Request ID right because I could terminate the instance after that.
          Hide
          thoulen FABRIZIO MANFREDI added a comment -

          It should be fixed in 1.45, now the plugin is waiting the ID of the node in case of the spot instance

          Show
          thoulen FABRIZIO MANFREDI added a comment - It should be fixed in 1.45, now the plugin is waiting the ID of the node in case of the spot instance

            People

            • Assignee:
              Unassigned
              Reporter:
              maneken Ruslan Bondarau
            • Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: