[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-41290 Timed out waiting for container to become ready! Change By: Jesse Glick Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178061.1485117354000.12848.1563306205032%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Carlos Sanchez commented on JENKINS-41290 Re: Timed out waiting for container to become ready! can you try the latest versions? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Pawel Daborowski edited a comment on JENKINS-41290
Re: Timed out waiting for container to become ready!
We have also encountered this bug when running podTemplate, but haven't identified the exact conditions in which this happens (we're not using inheritFrom).Our workaround was adding empty args string when executing cat. { { code:java} podTemplate( }} {{ label: podName, }} {{ containers: [ }} {{ jenkins. containerTemplate(name: builder, image: image, workingDir: '/root', ttyEnabled: true, command: 'cat', args: '') }} {{ ], {code } } If we don't do that (run command without args), the generated PodTemplate section in "Configure System" contains 'cat' in command line and another 'cat' in arguments line.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Pawel Daborowski edited a comment on JENKINS-41290
Re: Timed out waiting for container to become ready!
We have also encountered this bug when running podTemplate, but haven't identified the exact conditions in which this happens (we're not using inheritFrom).Our workaround was adding empty args string when executing cat. { quote} { podTemplate( }} {{ label: podName, }} {{ containers: [ }} {{ jenkins.containerTemplate(name: builder, image: image, workingDir: '/root', ttyEnabled: true, command: 'cat', args: '') }} {{ ], {quote } } If we don't do that (run command without args), the generated PodTemplate section in "Configure System" contains 'cat' in command line and another 'cat' in arguments line.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Pawel Daborowski commented on JENKINS-41290 Re: Timed out waiting for container to become ready! We have also encountered this bug when running podTemplate, but haven't identified the exact conditions in which this happens (we're not using inheritFrom). Our workaround was adding empty args string when executing cat. podTemplate( label: podName, containers: [ jenkins.containerTemplate(name: builder, image: image, workingDir: '/root', ttyEnabled: true, command: 'cat', args: '') ], If we don't do that (run command without args), the generated PodTemplate section in "Configure System" contains 'cat' in command line and another 'cat' in arguments line. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Jae Choi commented on JENKINS-41290 Re: Timed out waiting for container to become ready! Note there is an issue when using with inheritFrom. It will hang forever with Proceeding Workaround is not to use inheritFrom but we may need to fix this issue in the code if possible Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Jae Choi commented on JENKINS-41290 Re: Timed out waiting for container to become ready! I found the reason why. It actually stores cat as an argument inside settings under podTemplate when it runs so when I saved my settings it persisted with that podTemplate with command cat and arg cat! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Jae Choi commented on JENKINS-41290 Re: Timed out waiting for container to become ready! No it's just containerTemplate(name: 'java', image: "java:8-jdk", command: 'cat', ttyEnabled: true), Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Ioannis Canellos commented on JENKINS-41290 Re: Timed out waiting for container to become ready! maybe both command and arguments are cat Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Jae Choi commented on JENKINS-41290
Re: Timed out waiting for container to become ready!
Yes I tried that aswell with command. Below is what I get:
11:42:13 > git rev-list f16b518a3bf9dab6bb26b2f180160bef0d197de2 # timeout=10
[Pipeline] container
[Pipeline] {
[Pipeline] stage (Testing volume mount)
11:42:13 Using the ?stage? step without a block argument is deprecated
11:42:13 Entering stage Testing volume mount
11:42:13 Proceeding
and hangs forever This is what I have inside the node.
78bbc1e0e5e1java:8-jdk "cat cat"2 minutes ago Exited (1) 2 minutes ago k8s_java.8e54b2d3_kubernetes-
Not sure why it's "cat cat" instead of just "cat"
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@g
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Ioannis Canellos commented on JENKINS-41290 Re: Timed out waiting for container to become ready! Well, in your case the 'java' container just exits normally. You need to give a command that will keep the container running. This is why we use the cat command. containerTemplate(name: 'java', image: "java:8-jdk", command: 'cat', ttyEnabled: true), Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Jae Choi edited a comment on JENKINS-41290
Re: Timed out waiting for container to become ready!
I can reproduce with below{code}#!groovytimestamps { podTemplate(label: 'test', containers: [containerTemplate(name: 'java', image: "java:8-jdk", ttyEnabled: true), ], volumes: [ hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock'), ]) {node ('test') {stage('Checkout') {git branch: 'jenkins_test', credentialsId: 'bitbucket', url: 'https://t...@bitbucket.company.com.au/scm/ap/test.git'container('java') {stage 'Testing shell command'sh "ls -la"}}} }}{code}Below is the output with errors{code}10:45:03 Waiting for container container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b] to become ready.[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] }[Pipeline] // timestamps[Pipeline] End of Pipelinejava.io.IOException: Failed to execute shell script inside container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:88) at hudson.Launcher$ProcStarter.start(Launcher.java:384) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:147) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:172) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:13) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.Continuation
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Jae Choi edited a comment on JENKINS-41290
Re: Timed out waiting for container to become ready!
I can reproduce with below{code}#!groovytimestamps { podTemplate(label: 'test', containers: [containerTemplate(name: 'java', image: "java:8-jdk", ttyEnabled: true), ], volumes: [ hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock'), ]) {node ('test') {stage('Checkout') {git branch: 'jenkins_test', credentialsId: 'bitbucket', url: 'https://t...@bitbucket.company.com.au/scm/ap/test.git'container('java') {stage 'Testing shell command'sh "ls -la"}}} }}{code}Below is the output with errors{code}10:45:03 Waiting for container container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b] to become ready.[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] }[Pipeline] // timestamps[Pipeline] End of Pipelinejava.io.IOException: Failed to execute shell script inside container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:88) at hudson.Launcher$ProcStarter.start(Launcher.java:384) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:147) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:172) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:13) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.Continuation
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Jae Choi edited a comment on JENKINS-41290
Re: Timed out waiting for container to become ready!
I can reproduce with below{code}#!groovytimestamps { podTemplate(label: 'test', containers: [containerTemplate(name: 'java', image: "java:8-jdk", ttyEnabled: true), ], volumes: [ hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock'), ]) {node ('test') {stage('Checkout') {git branch: 'jenkins_test', credentialsId: 'bitbucket', url: 'https://t...@bitbucket.company.com.au/scm/ap/test.git'container('java') {stage 'Testing shell command'sh "ls -la"}}} }}{code} Below is the output with errors{code}10:45:03 Waiting for container container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b] to become ready.[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] }[Pipeline] // timestamps[Pipeline] End of Pipelinejava.io.IOException: Failed to execute shell script inside container [java] of pod [kubernetes-f4c6529a75c24a49ba5832745b9524b7-21cedef85a92b]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:88) at hudson.Launcher$ProcStarter.start(Launcher.java:384) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:147) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:172) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:13) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.Continuatio
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Jae Choi commented on JENKINS-41290
Re: Timed out waiting for container to become ready!
I can reproduce with below
#!groovy
timestamps {
podTemplate(label: 'test', containers: [
containerTemplate(name: 'java', image: "java:8-jdk", ttyEnabled: true),
], volumes: [
hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock'),
]) {
node ('test') {
stage('Checkout') {
git branch: 'jenkins_test', credentialsId: 'bitbucket', url: 'https://t...@bitbucket.company.com.au/scm/ap/test.git'
container('java') {
stage 'Testing shell command'
sh "ls -la"
}
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Anton Hughes commented on JENKINS-41290 Re: Timed out waiting for container to become ready! I suggest we close this as I'm now unable to reproduce it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Ioannis Canellos commented on JENKINS-41290 Re: Timed out waiting for container to become ready! Hard to tell what's going on with the available information. We need to see why the pod is not getting ready. For that we need at least an `oc describe` for the failing pod. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Jae Choi commented on JENKINS-41290 Re: Timed out waiting for container to become ready! Was there any update on this? We cannot use containertemplate at all Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Ioannis Canellos commented on JENKINS-41290 Re: Timed out waiting for container to become ready! This error can occur if the target container is not found or if its not ready. Can you please paste the output of `oc get pods`? And then it would also help if we could get an `oc describe` for the kubernetes- pod. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Anton Hughes commented on JENKINS-41290 Re: Timed out waiting for container to become ready! The log from the Jenkins pod is: NFO: Finished Download metadata. 6,467 ms --> setting agent port for jnlp --> setting agent port for jnlp... done Jan 23, 2017 9:11:08 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started Gravatar periodic lookup Jan 23, 2017 9:11:08 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Gravatar periodic lookup. 1 ms Jan 23, 2017 9:11:23 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: shiftwork-staffservice-pipeline-dev #21 completed: FAILURE Jan 23, 2017 9:11:23 PM io.jenkins.blueocean.events.PipelineEventListener$1 run SEVERE: Unexpected error publishing pipeline FlowNode event. java.util.concurrent.ExecutionException: hudson.AbortException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at io.jenkins.blueocean.events.PipelineEventListener$1.run(PipelineEventListener.java:226) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.AbortException at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1068) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) I cannot see any pods that fail to start. Add Comment
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title Carlos Sanchez commented on JENKINS-41290 Re: Timed out waiting for container to become ready! you need to check in kubernetes/openshift why the pods failed to start Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41290) Timed out waiting for container to become ready!
Title: Message Title
Anton Hughes created an issue
Jenkins / JENKINS-41290
Timed out waiting for container to become ready!
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Jan/22 8:35 PM
Priority:
Critical
Reporter:
Anton Hughes
When running the following jenkins file in OpenShift, it always errrors Jenkinsfile
#!/usr/bin/groovy
@Library('github.com/fabric8io/fabric8-pipeline-library@master')
// lets allow the VERSION_PREFIX to be specified as a parameter to the build
// but if not lets just default to 1.0
def versionPrefix = ""
try {
versionPrefix = VERSION_PREFIX
} catch (Throwable e) {
versionPrefix = "1.0"
}
def canaryVersion = "${versionPrefix}.${env.BUILD_NUMBER}"
//def label = "buildpod.${env.JOB_NAME}.${env.BUILD_NUMBER}".replace('-', '_').replace('/', '_')
def label = "master"
podTemplate(label: label, serviceAccount: 'jenkins', containers: [
[name: 'maven', image: 'fabric8/maven-builder', command: 'cat', ttyEnabled: true, envVars: [
[key: 'MAVEN_OPTS', value:'-Duser.home=/home/jenkins/'],
[key: 'DOCKER_CONFIG', value:'/home/jenkins/.docker/'],
[key: 'KUBERNETES_MASTER', value: 'kubernetes.default'] ]],
[name: 'jnlp', image: 'iocanel/jenkins-jnlp-client:latest', command:'/usr/local/bin/start.sh', args: '${computer.jnlpmac} ${computer.name}', ttyEnabled: false,
envVars: [[key: 'DOCKER_HOST', value: 'unix:/var/run/docker.sock',
volumes: [
[$class: 'PersistentVolumeClaim', mountPath: '/home/jenkins/.mvnrepository', claimName: 'jenkins-mvn-local-repo'],
[$class: 'SecretVolume', mountPath: '/home/jenkins/.m2/', secretName: 'jenkins-maven-settings'],
[$class: 'SecretVolume', mountPath: '/home/jenkins/.do
