[JIRA] (JENKINS-53062) k8s slave should automatically deleted

6 views
Skip to first unread message

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 2:33:02 AM8/16/18
to jenkinsc...@googlegroups.com
runze xia created an issue
 
Jenkins / Improvement JENKINS-53062
k8s slave should automatically deleted
Issue Type: Improvement Improvement
Assignee: Carlos Sanchez
Components: kubernetes-plugin
Created: 2018-08-16 06:32
Priority: Minor Minor
Reporter: runze xia

If the jenkins job is deleted while the pipeline is running, the k8s slave cannot be deleted automatically.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

jenkins-ci@carlossanchez.eu (JIRA)

unread,
Aug 16, 2018, 5:39:01 AM8/16/18
to jenkinsc...@googlegroups.com

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 5:44:01 AM8/16/18
to jenkinsc...@googlegroups.com

The jenkins job has been deleted, so there is no related log, but this is very easy to reproduce, you need to start a build and delete the job while the build is still running.

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 5:46:02 AM8/16/18
to jenkinsc...@googlegroups.com
runze xia updated an issue
 
Change By: runze xia
Comment:
The jenkins job has been deleted, so there is no related log, but this is very easy to reproduce, you need to start a build and delete the job while the build is still running.

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 5:47:02 AM8/16/18
to jenkinsc...@googlegroups.com
 
Re: k8s slave should automatically deleted

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

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 5:48:02 AM8/16/18
to jenkinsc...@googlegroups.com

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.

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 6:07:02 AM8/16/18
to jenkinsc...@googlegroups.com
runze xia updated an issue
Change By: runze xia
Attachment: screenshot-1.png

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 6:09:02 AM8/16/18
to jenkinsc...@googlegroups.com
 
Re: k8s slave should automatically deleted


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

root@junwuhui.cn (JIRA)

unread,
Aug 16, 2018, 6:12:01 AM8/16/18
to jenkinsc...@googlegroups.com

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.

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:43:42 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Unassigned
 
Change By: Jesse Glick
Assignee: Carlos Sanchez
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

karl-philipp.richter@orgavision.com (JIRA)

unread,
Apr 9, 2020, 9:03:02 AM4/9/20
to jenkinsc...@googlegroups.com
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

karl-philipp.richter@orgavision.com (JIRA)

unread,
Apr 9, 2020, 9:20:03 AM4/9/20
to jenkinsc...@googlegroups.com
Possible duplicate of https://issues.jenkins-ci.org/browse/JENKINS- 53431 54540
Reply all
Reply to author
Forward
0 new messages