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

ec2-fleet plugin can no longer connect to nodes on Jenkins version 2.54

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not A Defect
    • ec2-fleet-plugin
    • None

    Description

      After upgrading from Jenkins version 2.53 to 2.54, the ec2-fleet-plugin can no longer connect to ec2-fleet nodes. Downgrading to 2.53 resolved the issue.

      Apr 11, 2017 6:44:41 PM hudson.slaves.SlaveComputer tryReconnect 
      INFO: Attempting to reconnect i-0253ae1397c99cef9 
      [04/11/17 18:44:45] SSH Launch of i-0253ae1397c99cef9 on 52.201.254.50 failed in 4,176 ms 
      Apr 11, 2017 6:44:45 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run 
      SEVERE: I/O error in channel i-0253ae1397c99cef9 
      java.io.IOException: Unexpected termination of the channel 
             at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) 
      Caused by: java.io.EOFException 
             at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2624) 
             at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3099) 
             at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853) 
             at java.io.ObjectInputStream.<init>(ObjectInputStream.java:349) 
             at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) 
             at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) 
             at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) 
      
      
      

      Attachments

        Activity

          oleg_nenashev Oleg Nenashev added a comment -

          Does ec2-fleet plugin configuration use Java 7? I would guess so

          oleg_nenashev Oleg Nenashev added a comment - Does ec2-fleet plugin configuration use Java 7? I would guess so
          toga98 Russ Tennant added a comment -

          oleg_nenashev I'm not sure if I understand your question. The Jenkins server runs on java 8.

          java version "1.8.0_121"
          Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
          Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
          
          toga98 Russ Tennant added a comment - oleg_nenashev I'm not sure if I understand your question. The Jenkins server runs on java 8. java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
          oleg_nenashev Oleg Nenashev added a comment -

          Sorry if I was not clear. The question was about Jenkins agents being connected by the plugin.

          oleg_nenashev Oleg Nenashev added a comment - Sorry if I was not clear. The question was about Jenkins agents being connected by the plugin.
          toga98 Russ Tennant added a comment -

          I think you're correct. I am fairly certain the secondary ec2 fleet node's run Java 7. I'll check in a bit and add a comment.

          toga98 Russ Tennant added a comment - I think you're correct. I am fairly certain the secondary ec2 fleet node's run Java 7. I'll check in a bit and add a comment.
          toga98 Russ Tennant added a comment -

          The ec2 fleet nodes are running Java 7

          java version "1.7.0_131"
          OpenJDK Runtime Environment (amzn-2.6.9.0.71.amzn1-x86_64 u131-b00)
          OpenJDK 64-Bit Server VM (build 24.131-b00, mixed mode)
          
          toga98 Russ Tennant added a comment - The ec2 fleet nodes are running Java 7 java version "1.7.0_131" OpenJDK Runtime Environment (amzn-2.6.9.0.71.amzn1-x86_64 u131-b00) OpenJDK 64-Bit Server VM (build 24.131-b00, mixed mode)
          oleg_nenashev Oleg Nenashev added a comment -

          The it is an "as designed" behavior. In 2.54 Jenkins' Java minimal requirement has been updated to Java 8, hence all agents need to be updated.

          oleg_nenashev Oleg Nenashev added a comment - The it is an "as designed" behavior. In 2.54 Jenkins' Java minimal requirement has been updated to Java 8, hence all agents need to be updated.

          People

            schmutze Chad Schmutzer
            toga98 Russ Tennant
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: