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

EOF from OkHttp in kubernetes plugin on AKS 5m after start of sh step

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      1.16.1

      Description

      When running the container step on AKS, after exactly five minutes a given sh step will print:

      java.io.EOFException
       	at okio.RealBufferedSource.require(RealBufferedSource.java:61)
       	at okio.RealBufferedSource.readByte(RealBufferedSource.java:74)
       	at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
       	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
       	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
       	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
       	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
       	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
       	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
       	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
       	at java.lang.Thread.run(Thread.java:748)
      

        Attachments

          Issue Links

            Activity

            Hide
            localhost Vivek Singh added a comment - - edited

            Same issue I am facing in Kubernetes Plugin 1.24.1.

            Pipeline steps are failing with the same error:

            java.io.EOFException
            at okio.RealBufferedSource.require(RealBufferedSource.java:61)
            at okio.RealBufferedSource.readByte(RealBufferedSource.java:74)
            at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
            at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
            at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
            at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
            at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
            at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at java.lang.Thread.run(Thread.java:748)

            If any one know the resolution please let me know.

            Show
            localhost Vivek Singh added a comment - - edited Same issue I am facing in Kubernetes Plugin 1.24.1. Pipeline steps are failing with the same error: java.io.EOFException at okio.RealBufferedSource.require(RealBufferedSource.java:61) at okio.RealBufferedSource.readByte(RealBufferedSource.java:74) at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) If any one know the resolution please let me know.
            Hide
            jglick Jesse Glick added a comment -

            Please do not reopen; this was a particular fix for a particular bug and the fix addressed that bug. Whatever you are encountering may or may not be related; the stack trace is too generic to really say anything. File a fresh bug, Link’ing it to this one, and provide complete steps to reproduce from scratch if you have them.

            Show
            jglick Jesse Glick added a comment - Please do not reopen; this was a particular fix for a particular bug and the fix addressed that bug. Whatever you are encountering may or may not be related; the stack trace is too generic to really say anything. File a fresh bug, Link ’ing it to this one, and provide complete steps to reproduce from scratch if you have them.

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              jglick Jesse Glick
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: