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

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • ec2-fleet-plugin
    • None

      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) 
      
      
      

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

              Created:
              Updated:
              Resolved: