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

Ec2 plugin: Cannot create windows node with ec2 1.50.3

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ec2-plugin
    • None
    • Jenkins 2.222.4
      ec2 plugin: 1.50.3

      I've tried to use the latest (1.50.3) version of the ec2 plugin and encountered an issue when creating a windows node.

      When trying to start the ec2 instance, it boots and then it got stuck. I didn't manage to find why. Here the only log I have:

       

      EC2 (elastic-cloud) - windows-node (i-1234) booted at 1591718074000
      Connecting to (xx.xx.xx.xx) with WinRM as Administrator

      Enabling the logging gave me no information. I was hoping having some logs enabling logging for hudson.plugins.ec2.win but without success

      The code seems stuck I don't have log saying it is doing something.

      I downgrade to 1.50.2.1 and it is working correctly. With the logging enabled I managed to get this line that I don't have with the 1.50.3

       

      Jun 09, 2020 4:05:31 PM FINE hudson.plugins.ec2.win.WinConnection checking SMB connection to xx.xx.xx.xx

       

       

       

          [JENKINS-62641] Ec2 plugin: Cannot create windows node with ec2 1.50.3

          Adrien Zieba created issue -
          Adrien Zieba made changes -
          Description Original: I've tried to use the latest (1.0.53) version of the ec2 plugin and encountered an issue when creating a windows node.

          When trying to start the ec2 instance, it boots and then it got stuck. I didn't manage to find why. Here the only log I have:

           
          {noformat}
          EC2 (elastic-cloud) - windows-node (i-1234) booted at 1591718074000
          Connecting to (xx.xx.xx.xx) with WinRM as Administrator{noformat}
          Enabling the logging gave me no information. I was hoping having some logs enabling logging for hudson.plugins.ec2.win but without success

          The code seems stuck I don't have log saying it is doing something.



          I downgrade to 1.0.52.1 and it is working correctly. With the logging enabled I managed to get this line that I don't have with the 1.0.53.1

           
          {noformat}
          Jun 09, 2020 4:05:31 PM FINE hudson.plugins.ec2.win.WinConnection checking SMB connection to 172.31.131.149{noformat}
           

           

           
          New: I've tried to use the latest (1.0.53) version of the ec2 plugin and encountered an issue when creating a windows node.

          When trying to start the ec2 instance, it boots and then it got stuck. I didn't manage to find why. Here the only log I have:

           
          {noformat}
          EC2 (elastic-cloud) - windows-node (i-1234) booted at 1591718074000
          Connecting to (xx.xx.xx.xx) with WinRM as Administrator{noformat}
          Enabling the logging gave me no information. I was hoping having some logs enabling logging for hudson.plugins.ec2.win but without success

          The code seems stuck I don't have log saying it is doing something.

          I downgrade to 1.0.52.1 and it is working correctly. With the logging enabled I managed to get this line that I don't have with the 1.0.53

           
          {noformat}
          Jun 09, 2020 4:05:31 PM FINE hudson.plugins.ec2.win.WinConnection checking SMB connection to 172.31.131.149{noformat}
           

           

           
          Adrien Zieba made changes -
          Description Original: I've tried to use the latest (1.0.53) version of the ec2 plugin and encountered an issue when creating a windows node.

          When trying to start the ec2 instance, it boots and then it got stuck. I didn't manage to find why. Here the only log I have:

           
          {noformat}
          EC2 (elastic-cloud) - windows-node (i-1234) booted at 1591718074000
          Connecting to (xx.xx.xx.xx) with WinRM as Administrator{noformat}
          Enabling the logging gave me no information. I was hoping having some logs enabling logging for hudson.plugins.ec2.win but without success

          The code seems stuck I don't have log saying it is doing something.

          I downgrade to 1.0.52.1 and it is working correctly. With the logging enabled I managed to get this line that I don't have with the 1.0.53

           
          {noformat}
          Jun 09, 2020 4:05:31 PM FINE hudson.plugins.ec2.win.WinConnection checking SMB connection to 172.31.131.149{noformat}
           

           

           
          New: I've tried to use the latest (1.0.53) version of the ec2 plugin and encountered an issue when creating a windows node.

          When trying to start the ec2 instance, it boots and then it got stuck. I didn't manage to find why. Here the only log I have:

           
          {noformat}
          EC2 (elastic-cloud) - windows-node (i-1234) booted at 1591718074000
          Connecting to (xx.xx.xx.xx) with WinRM as Administrator{noformat}
          Enabling the logging gave me no information. I was hoping having some logs enabling logging for hudson.plugins.ec2.win but without success

          The code seems stuck I don't have log saying it is doing something.

          I downgrade to 1.0.52.1 and it is working correctly. With the logging enabled I managed to get this line that I don't have with the 1.0.53

           
          {noformat}
          Jun 09, 2020 4:05:31 PM FINE hudson.plugins.ec2.win.WinConnection checking SMB connection to xx.xx.xx.xx{noformat}
           

           

           

          Kyle L added a comment -

          I'm experiencing this same issue with 1.0.53. In watching tcpdump, it's not attempting to make any connections on 445 or 5985. Also, nothing useful in the logs.

          Kyle L added a comment - I'm experiencing this same issue with 1.0.53. In watching tcpdump, it's not attempting to make any connections on 445 or 5985. Also, nothing useful in the logs.

          Dave Barker added a comment - - edited

          I've seen similar behavior. On 1.50.2  I've been able to work around the issue by deleting the agent on the hung EC2 instance via the Jenkins console.  I will have a VM, that was created by the plug-in overnight that is hung on startup   Once that agent is deleted the plugin spins up another instance and the job runs normally.  

          On 1.50.3 The work around does not work.  Any Windows VM the ec2 plugin starts never starts up successfully.

          I reverted to 1.50.2.

          Dave Barker added a comment - - edited I've seen similar behavior. On 1.50.2  I've been able to work around the issue by deleting the agent on the hung EC2 instance via the Jenkins console.  I will have a VM, that was created by the plug-in overnight that is hung on startup   Once that agent is deleted the plugin spins up another instance and the job runs normally.   On 1.50.3 The work around does not work.  Any Windows VM the ec2 plugin starts never starts up successfully. I reverted to 1.50.2.

          We're experiencing same issue with EC2 plugin.
          Jenkins Version: 2.235.1

          EC2 plugin: 1.50.3
          In order to work I have to downgrade EC2 plugin to 1.45. Any version between 1.46 and 1.50.3 is failing to launch Windows machine (EC2)

          Lakshmi Ravipati added a comment - We're experiencing same issue with EC2 plugin. Jenkins Version: 2.235.1 EC2 plugin: 1.50.3 In order to work I have to downgrade EC2 plugin to 1.45. Any version between 1.46 and 1.50.3 is failing to launch Windows machine (EC2)

          tapvir virk added a comment - - edited

          I am also facing the same issue.
          For now, as suggested, I will point to 1.50.2

          Looking forward for a fix

          tapvir virk added a comment - - edited I am also facing the same issue. For now, as suggested, I will point to 1.50.2 Looking forward for a fix

          Alexey Yambarshev added a comment - - edited

          Jenkins 2.222.4 with EC2 plugin 1.50.3 launches EC2 nodes (Windows as well).
          But it works with VPC in our case.
          We set following parameters for AMIs:

          • "Security group names"
          • "Subnet IDs for VPC"

          Alexey Yambarshev added a comment - - edited Jenkins 2.222.4 with EC2 plugin 1.50.3 launches EC2 nodes (Windows as well). But it works with VPC in our case. We set following parameters for AMIs: "Security group names" "Subnet IDs for VPC"
          Owen Mehegan made changes -
          Summary Original: Ec2 plugin: Cannot create windows node with ec2 1.0.50.3 New: Ec2 plugin: Cannot create windows node with ec2 1.50.3
          Owen Mehegan made changes -
          Environment Original: Jenkins 2.222.4
          ec2 plugin: 1.0.53
          New: Jenkins 2.222.4
          ec2 plugin: 1.50.3

            thoulen FABRIZIO MANFREDI
            adrienzieba Adrien Zieba
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: