• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • kubernetes-plugin
    • None

      If the jenkins job is deleted while the pipeline is running, the k8s slave cannot be deleted automatically.

          [JENKINS-53062] k8s slave should automatically deleted

          Carlos Sanchez added a comment - logs ? https://github.com/jenkinsci/kubernetes-plugin#debugging

          runze xia added a comment -

          Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main createEngine
          INFO: Setting up agent: jenkins-slave-kp9w7-080vf
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener <init>
          INFO: Jenkins agent is running in headless mode.
          Aug 16, 2018 9:43:28 AM hudson.remoting.Engine startEngine
          INFO: Using Remoting version: 3.19
          Aug 16, 2018 9:43:28 AM hudson.remoting.Engine startEngine
          WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Locating server among http://192.168.0.2:8080/
          Aug 16, 2018 9:43:28 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
          INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Agent discovery successful
          Agent address: 192.168.0.2
          Agent port: 50000
          Identity: 98:9a:10:d2:0b:01:f0:4a:34:5b:f2:cb:bf:03:49:41
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Handshaking
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Connecting to 192.168.0.2:50000
          Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Trying protocol: JNLP4-connect
          Aug 16, 2018 9:43:29 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Remote identity confirmed: 98:9a:10:d2:0b:01:f0:4a:34:5b:f2:cb:bf:03:49:41
          Aug 16, 2018 9:43:30 AM hudson.remoting.jnlp.Main$CuiListener status
          INFO: Connected

          runze xia added a comment - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: jenkins-slave-kp9w7-080vf Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Aug 16, 2018 9:43:28 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.19 Aug 16, 2018 9:43:28 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://192.168.0.2:8080/ Aug 16, 2018 9:43:28 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: 192.168.0.2 Agent port: 50000 Identity: 98:9a:10:d2:0b:01:f0:4a:34:5b:f2:cb:bf:03:49:41 Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 192.168.0.2:50000 Aug 16, 2018 9:43:28 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Aug 16, 2018 9:43:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: 98:9a:10:d2:0b:01:f0:4a:34:5b:f2:cb:bf:03:49:41 Aug 16, 2018 9:43:30 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected

          runze xia added a comment -

          It's not easy to find the problem from the log, but this is very easy to reproduce, you need to start a build and delete the job while the build is still running.

          runze xia added a comment - It's not easy to find the problem from the log, but this is very easy to reproduce, you need to start a build and delete the job while the build is still running.

          runze xia added a comment -


          In order to reproduce this problem, you can quickly trigger multiple builds and then delete the jenkins job.

          runze xia added a comment - In order to reproduce this problem, you can quickly trigger multiple builds and then delete the jenkins job.

          runze xia added a comment -

          In my observations, it was found that not all pods could not be deleted correctly. I guess there is a problem with the pod in the creating state.

          runze xia added a comment - In my observations, it was found that not all pods could not be deleted correctly. I guess there is a problem with the pod in the creating state.

          Karl-Philipp Richter added a comment - - edited

          Karl-Philipp Richter added a comment - - edited Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS-54540

            Unassigned Unassigned
            runzexia runze xia
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: