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

exception thrown when automatically deleting old workers

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: openstack-cloud-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.619
      MacOS 10.10.3
      openstack-jcloud-plugin 1.8
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            alskor Alex Java added a comment -

            this may be related to (or even duplicates) almost identical JIRAs - see links.

            Show
            alskor Alex Java added a comment - this may be related to (or even duplicates) almost identical JIRAs - see links.
            Hide
            olivergondza Oliver Gondža added a comment -

            My best guess is that the machine is returned to openstack but slave connection is not closed properly so it fails when machines stops responding. The fact that this is the only symptom supports that hypothesis.

            Show
            olivergondza Oliver Gondža added a comment - My best guess is that the machine is returned to openstack but slave connection is not closed properly so it fails when machines stops responding. The fact that this is the only symptom supports that hypothesis.

              People

              Assignee:
              mavlyutov Marat Mavlyutov
              Reporter:
              alskor Alex Java
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: