I see a bunch of these stacktraces in Jenkins console.
they started to appear when openstack-cloud-plugin tried to remove some old workers (which were supposed to be deleted because of their retention policy of 2 minutes).

Jul 21, 2015 6:18:11 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel alex-openstack-medium-73d
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2328)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2797)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

at the end, I see that all worker nodes were successfully deleted in both Jenkins and Openstack cluster (although I saw several bursts of these exceptions).

this exception can give impression that things are broken and people will have to spend hours debugging this...
it would be nice to fix this, even if it's a kinda-harmless error message.