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

Spot instances not getting their userdata settings

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ec2-plugin
    • None
    • ec2-plugin 1.32
      Jenkins 1.651.1 LTS
      Slave Windows 2012r2
      Master AWS linux

      Hi.

      Updated to the latest stable ec2-plugin and now found that the jnlp method for using spot instances has stopped working.

      We use it as its worked before and was the easiest to get working.

      From looking at the instance the userdata is blank so it does not look like it is getting set.

          [JENKINS-34702] Spot instances not getting their userdata settings

          probably a documentation issue, also the AMI scripts probably should go if this feature has been removed.

          John-Paul Drawneek added a comment - probably a documentation issue, also the AMI scripts probably should go if this feature has been removed.

          Ryan Aslett added a comment - - edited

          The documentation on the plugin page says that you need to set up a script to parse the user-data and reconnect back to jenkins.

          We used to do some setup on boot and then connect to jenkins once that setup is finished, but now SSH is ready before our rc.local scripts run, and the node isnt actually ready for builds (we do some tmpfs creation and directory building).

          We've worked around this by having our rc.local script touch a ~/.jenkins_ready file, and added a simple init script to the ami configuration of

          {{
          while [ ! -f ~/.jenkins_ready ]
          do
          sleep 1
          done
          }}

          The documenation definitely needs to be updated ...

          Ryan Aslett added a comment - - edited The documentation on the plugin page says that you need to set up a script to parse the user-data and reconnect back to jenkins. We used to do some setup on boot and then connect to jenkins once that setup is finished, but now SSH is ready before our rc.local scripts run, and the node isnt actually ready for builds (we do some tmpfs creation and directory building). We've worked around this by having our rc.local script touch a ~/.jenkins_ready file, and added a simple init script to the ami configuration of {{ while [ ! -f ~/.jenkins_ready ] do sleep 1 done }} The documenation definitely needs to be updated ...

          Michael added a comment -

          Hi,

          This is still a problem in version `1.59` - has there been no traction to get this resolved? I spend some time getting everything setup ready to use Spot instances and it's failing at the last hurdle.

           

          Alternatively, can you tell me which version of the plugin was still creating the userData on the EC2 instances for Spot?

          Thanks

          Michael added a comment - Hi, This is still a problem in version `1.59` - has there been no traction to get this resolved? I spend some time getting everything setup ready to use Spot instances and it's failing at the last hurdle.   Alternatively, can you tell me which version of the plugin was still creating the userData on the EC2 instances for Spot? Thanks

            francisu Francis Upton
            jpd4nt John-Paul Drawneek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: