[JIRA] (JENKINS-47561) Pipelines wait indefinitely for kubernetes slaves to come back online

5 views
Skip to first unread message

jenkins-ci@carlossanchez.eu (JIRA)

unread,
Mar 20, 2018, 7:15:02 AM3/20/18
to jenkinsc...@googlegroups.com
Carlos Sanchez resolved as Cannot Reproduce
 

I don't see this problem with the latest versions of the plugin. Reopen if that is not the case

Jenkins / Bug JENKINS-47561
Pipelines wait indefinitely for kubernetes slaves to come back online
Change By: Carlos Sanchez
Status: Open Resolved
Resolution: Cannot Reproduce
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

rishirt.us@gmail.com (JIRA)

unread,
Jun 10, 2019, 7:06:02 PM6/10/19
to jenkinsc...@googlegroups.com
Rishi Thakkar reopened an issue
 

I still see this issue in the newest version of the plugin.

 

The pod runs out of ephemeral storage and the JNLP agent dies. Then, the build step gets stuck indefinitely.

Change By: Rishi Thakkar
Resolution: Cannot Reproduce
Status: Resolved Reopened
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

arun.kaushik@salesforce.com (JIRA)

unread,
Jul 8, 2019, 8:58:01 AM7/8/19
to jenkinsc...@googlegroups.com
Arun Kaushik commented on Bug JENKINS-47561
 
Re: Pipelines wait indefinitely for kubernetes slaves to come back online

We are using 1.14.9 version on kubernetes-plugin and still facing this issue. We pass CPU/Memory limits in container template and when those limits are reached, the container is killed, leaving the build in stalled state for ever. Seems like Jenkins master never gets to know that slave is decommissioned intentionally and it has to move on and fail the build. 

Reply all
Reply to author
Forward
0 new messages