Kubernetes plugin - ready probe

115 views
Skip to first unread message

Romain Grécourt

unread,
Nov 17, 2018, 7:47:01 AM11/17/18
to jenkins...@googlegroups.com
Hi,

I'm doing a Jenkins pipeline with the kubernetes plugin (1.12.4).

Currently facing some odd behaviors where steps are executed before the pod is actually "ready". See some of the errors  I got below.

One of the recurring error is about a non existing directory inside the workspace, or the main container not existing in the pod.

BTW, what's exit code -2 ?

Looking at the pod definition I don't see any probe for the injected jnlp container.
Should I define a probe to ensure a proper readiness ? Does anyone have recommendations on how to do this the right way ?


Thanks,
Romain

----
[ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ] Running shell script

process apparently never started in /home/jenkins/workspace/ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ@tmp/durable-3fb9a8c3

script returned exit code -2
----
[ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ] Running shell script

container [glassfish-ci] does not exist in pod [jenkins-slave-p3p21-whthx]
----
[ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ] Running shell script

process apparently never started in /home/jenkins/workspace/ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ@tmp/durable-fecb2d64

sh: 1: cannot create /home/jenkins/workspace/ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ@tmp/durable-fecb2d64/jenkins-log.txt: Directory nonexistent

sh: 1: cannot create /home/jenkins/workspace/ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ@tmp/durable-fecb2d64/jenkins-result.txt.tmp: Directory nonexistent

mv: cannot stat '/home/jenkins/workspace/ee4j-glassfish_ci-pipeline-YWJPM77PBRNTKWL4JGYGVAYHJW5MFPG52VIUHMUAGFIJ2G7NYJHQ@tmp/durable-fecb2d64/jenkins-result.txt.tmp': No such file or directory

script returned exit code -2
----

Carlos Sanchez

unread,
Nov 19, 2018, 2:56:55 AM11/19/18
to jenkins...@googlegroups.com
you need to check your pod logs and k8s describe them to see what's the possible error

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADhPohneMZ5%3Da2GPb5chSsjjRYctaJaDQbEXuKhBALO-N83o_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Romain Grécourt

unread,
Nov 19, 2018, 1:44:14 PM11/19/18
to jenkins...@googlegroups.com
Unfortunately I don't have cluster access (eclipse policy) and this issue is somewhat intermittent.
Will get back to you if/when I get these logs.

Carlos Sanchez

unread,
Nov 19, 2018, 4:09:15 PM11/19/18
to jenkins...@googlegroups.com
the latest agent logs may be in the jenkins logs if the agent fails to start

Reply all
Reply to author
Forward
0 new messages