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

          tapvir virk added a comment -

          Hi mramonleon - I already have security groups and subnet id's configured. THough my Jenkins version is 2.235.1

          I tried Host Key Verification to set it to off. Still doesn't work.

          Thanks

          tapvir virk added a comment - Hi mramonleon - I already have security groups and subnet id's configured. THough my Jenkins version is 2.235.1 I tried Host Key Verification to set it to off. Still doesn't work. Thanks

          Dave Barker added a comment -

          I'll have to tweak with versions in this configuration.  I do have the two fields set ayambarshev mentions.  I always have.

          Dave Barker added a comment - I'll have to tweak with versions in this configuration.  I do have the two fields set ayambarshev mentions.  I always have.

          tapvir virk added a comment -

          dbarker - What do you mean by tweak with versions in this configuration?

          tapvir virk added a comment - dbarker - What do you mean by tweak with versions in this configuration?

          Dave Barker added a comment -

          I'm on Jenkins 2.235.1

          Dave Barker added a comment - I'm on Jenkins 2.235.1

          tapvir virk added a comment -

          dbarker - I'm on the same version. Are you able to attach the windows slave?

          tapvir virk added a comment - dbarker - I'm on the same version. Are you able to attach the windows slave?

          Adrien Zieba added a comment -

          On my side I have a configuration similar to ayambarshev but I still have an issue with provisioning windows nodes.

          Adrien Zieba added a comment - On my side I have a configuration similar to ayambarshev but I still have an issue with provisioning windows nodes.

          tapvir virk added a comment -

          Same with me

          tapvir virk added a comment - Same with me

          Dave Barker added a comment -

          I am able to RDP into the node Jenkins won't connect to.  

          Dave Barker added a comment - I am able to RDP into the node Jenkins won't connect to.  

          tapvir virk added a comment -

          I believe which is fine and is not related to the issue. As jenkins using winrm in order to connect to windows instance.

          Is the windows slave gets connected succesfully to your jenkins master?

          tapvir virk added a comment - I believe which is fine and is not related to the issue. As jenkins using winrm in order to connect to windows instance. Is the windows slave gets connected succesfully to your jenkins master?

          Alexey Yambarshev added a comment - - edited

          One more note.
          We uses Jenkins outside AWS.
          So, the following significant fields are actual for us in Jenkins (in Advanced subfields for each AMI):
           - Connection Strategy - Public IP
           - Host Key Verification Strategy - accept-new  . It will be updated in the future for security when we update all necessary keys in AMI and Jenkins.

          Alexey Yambarshev added a comment - - edited One more note. We uses Jenkins outside AWS . So, the following significant fields are actual for us in Jenkins (in Advanced subfields for each AMI):  - Connection Strategy - Public IP  - Host Key Verification Strategy - accept-new   . It will be updated in the future for security when we update all necessary keys in AMI and Jenkins.

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

              Created:
              Updated: