[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
runze xia edited a comment on JENKINS-40294
Re: Exec Failure: HTTP:404. Message:Not Found
Jenkins v2.176.2 kubernetes plugin 1.15.10i also encountered the same problemThere is only one podtemplate with label xx in my jenkins.This problem occurs when I start a large number of agents at the same time.Belog is the agent log{code:java}Inbound agent connected from 10.233.103.249/10.233.103.249Waiting for agent to connect (0/100): maven-dws8pWaiting for agent to connect (1/100): maven-dws8pRemoting version: 3.27This is a Unix agentWaiting for agent to connect (2/100): maven-dws8pWaiting for agent to connect (3/100): maven-dws8pWaiting for agent to connect (4/100): maven-dws8pWaiting for agent to connect (5/100): maven-dws8pWaiting for agent to connect (6/100): maven-dws8pWaiting for agent to connect (7/100): maven-dws8pWaiting for agent to connect (8/100): maven-dws8pWaiting for agent to connect (9/100): maven-dws8pWaiting for agent to connect (10/100): maven-dws8pWaiting for agent to connect (11/100): maven-dws8pWaiting for agent to connect (12/100): maven-dws8pWaiting for agent to connect (13/100): maven-dws8pWaiting for agent to connect (14/100): maven-dws8pWaiting for agent to connect (15/100): maven-dws8pWaiting for agent to connect (16/100): maven-dws8pERROR: Failed to monitor for Free Temp Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)ERROR: Failed to monitor for Free Disk Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)Agent successfully connected and online{code}At the same time, there is a very interesting behavior. Some of the steps in the container step are executed successfully, and some steps have a probability of failing.The state of pod is Running. If a task is assigned to that agent again, it may succeed. !image-2019-09-18-14-04-48-431.png|thumbnail!
Add Comment
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
runze xia edited a comment on JENKINS-40294
Re: Exec Failure: HTTP:404. Message:Not Found
Jenkins v2.176.2 kubernetes plugin 1.15.10i also encountered the same problemThere is only one podtemplate with label xx in my jenkins.This problem occurs when I start a large number of agents at the same time.Belog is the agent log{code:java}Inbound agent connected from 10.233.103.249/10.233.103.249Waiting for agent to connect (0/100): maven-dws8pWaiting for agent to connect (1/100): maven-dws8pRemoting version: 3.27This is a Unix agentWaiting for agent to connect (2/100): maven-dws8pWaiting for agent to connect (3/100): maven-dws8pWaiting for agent to connect (4/100): maven-dws8pWaiting for agent to connect (5/100): maven-dws8pWaiting for agent to connect (6/100): maven-dws8pWaiting for agent to connect (7/100): maven-dws8pWaiting for agent to connect (8/100): maven-dws8pWaiting for agent to connect (9/100): maven-dws8pWaiting for agent to connect (10/100): maven-dws8pWaiting for agent to connect (11/100): maven-dws8pWaiting for agent to connect (12/100): maven-dws8pWaiting for agent to connect (13/100): maven-dws8pWaiting for agent to connect (14/100): maven-dws8pWaiting for agent to connect (15/100): maven-dws8pWaiting for agent to connect (16/100): maven-dws8pERROR: Failed to monitor for Free Temp Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)ERROR: Failed to monitor for Free Disk Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)Agent successfully connected and online{code} At the same time, there is a very interesting behavior. Some of the steps in the container step are executed successfully, and some steps have a probability of failing.The state of pod is Running. If a task is assigned to that agent again, it may succeed.
Add Comment
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
runze xia edited a comment on JENKINS-40294
Re: Exec Failure: HTTP:404. Message:Not Found
Jenkins v2.176.2 kubernetes plugin 1.15.10 i also encountered the same problemThere is only one podtemplate with label xx in my jenkins.This problem occurs when I start a large number of agents at the same time.Belog is the agent log{code:java}Inbound agent connected from 10.233.103.249/10.233.103.249Waiting for agent to connect (0/100): maven-dws8pWaiting for agent to connect (1/100): maven-dws8pRemoting version: 3.27This is a Unix agentWaiting for agent to connect (2/100): maven-dws8pWaiting for agent to connect (3/100): maven-dws8pWaiting for agent to connect (4/100): maven-dws8pWaiting for agent to connect (5/100): maven-dws8pWaiting for agent to connect (6/100): maven-dws8pWaiting for agent to connect (7/100): maven-dws8pWaiting for agent to connect (8/100): maven-dws8pWaiting for agent to connect (9/100): maven-dws8pWaiting for agent to connect (10/100): maven-dws8pWaiting for agent to connect (11/100): maven-dws8pWaiting for agent to connect (12/100): maven-dws8pWaiting for agent to connect (13/100): maven-dws8pWaiting for agent to connect (14/100): maven-dws8pWaiting for agent to connect (15/100): maven-dws8pWaiting for agent to connect (16/100): maven-dws8pERROR: Failed to monitor for Free Temp Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)ERROR: Failed to monitor for Free Disk Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303)Agent successfully connected and online{code}
Add Comment
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title runze xia reopened an issue i also encountered the same problem There is only one podtemplate with label xx in my jenkins. This problem occurs when I start a large number of agents at the same time. Belog is the agent log Inbound agent connected from 10.233.103.249/10.233.103.249 Waiting for agent to connect (0/100): maven-dws8p Waiting for agent to connect (1/100): maven-dws8p Remoting version: 3.27 This is a Unix agent Waiting for agent to connect (2/100): maven-dws8p Waiting for agent to connect (3/100): maven-dws8p Waiting for agent to connect (4/100): maven-dws8p Waiting for agent to connect (5/100): maven-dws8p Waiting for agent to connect (6/100): maven-dws8p Waiting for agent to connect (7/100): maven-dws8p Waiting for agent to connect (8/100): maven-dws8p Waiting for agent to connect (9/100): maven-dws8p Waiting for agent to connect (10/100): maven-dws8p Waiting for agent to connect (11/100): maven-dws8p Waiting for agent to connect (12/100): maven-dws8p Waiting for agent to connect (13/100): maven-dws8p Waiting for agent to connect (14/100): maven-dws8p Waiting for agent to connect (15/100): maven-dws8p Waiting for agent to connect (16/100): maven-dws8p ERROR: Failed to monitor for Free Temp Space java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303) ERROR: Failed to monitor for Free Disk Space java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:316) at hudson.remoting.Request$1.get(Request.java:240) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:303) Agent successfully connected and online Jenkins / JENKINS-40294 Exec Failure: HTTP:404. Message:Not Found Change By: runze xia Resolution: Not A Defect
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Carlos Sanchez resolved as Not A Defect so your pipeline is probably getting a different pod template because you have one in the global config with the same label. And that template doesn't have the container you are trying to exec into Jenkins / JENKINS-40294 Exec Failure: HTTP:404. Message:Not Found Change By: Carlos Sanchez Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Carlos Sanchez commented on JENKINS-40294 Re: Exec Failure: HTTP:404. Message:Not Found as I said, is there anything in the slave logs in jenkins web ui under /computer/xxx/log ? 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Jesse Redl commented on JENKINS-40294 Re: Exec Failure: HTTP:404. Message:Not Found Carlos Sanchez I also am encountering this exact error. I pulled the following logs out of my GKE logs: Dec 21, 2016 11:51:37 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Dec 21, 2016 11:51:37 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 Dec 21, 2016 11:51:37 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Created Pod: default-11ea535e917446 Dec 21, 2016 11:51:37 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Waiting for Pod to be scheduled (0/100): default-11ea535e917446 Dec 21, 2016 11:51:39 PM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #21 from /10.156.3.229:38600 Dec 21, 2016 11:51:39 PM hudson.TcpSlaveAgentListener$ConnectionHandler error WARNING: Connection #21 is aborted: Disabled protocol:Protocol:JNLP3-connect Dec 21, 2016 11:51:39 PM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted connection #22 from /10.156.3.229:38602 Dec 21, 2016 11:51:43 PM io.fabric8.kubernetes.client.dsl.internal.ExecWebSocketListener onFailure SEVERE: Exec Failure: HTTP:400. Message:Bad Request java.net.ProtocolException: Expected HTTP 101 response but was '400 Bad Request' at com.squareup.okhttp.ws.WebSocketCall.createWebSocket(WebSocketCall.java:123) at com.squareup.okhttp.ws.WebSocketCall.access$000(WebSocketCall.java:40) at com.squareup.okhttp.ws.WebSocketCall$1.onResponse(WebSocketCall.java:98) at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:177) at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33) 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) Dec 21, 2016 11:51:43 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate INFO: Terminating Kubernetes instance for slave default-11ea535e917446 Dec 21, 2016 11:51:43 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate INFO: Terminated Kubernetes instance for slave default-11ea535e917446 Dec 21, 2016 11:51:43 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate INFO: Disconnected computer default-11ea535e917446 Dec 21, 2016 11:51:43 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: vendasta/AA/jenkins-build #58 completed: FAILURE Dec 21, 2016 11:51:43 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call SEVERE: Error in provisioning; slave=KubernetesSlave name: default-11ea535e917446, template=org.csanchez.jenkins.plugins.kubernetes.PodTemplate@28a6c5c2 java.lang.IllegalStateException: Node was deleted, computer is null at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:556) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:482) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Carlos Sanchez commented on JENKINS-40294 Re: Exec Failure: HTTP:404. Message:Not Found are there any errors in the slave log? under /computer/xxx/log 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Val Orekhov updated an issue Jenkins / JENKINS-40294 Exec Failure: HTTP:404. Message:Not Found Change By: Val Orekhov Priority: Minor Critical 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title Val Orekhov commented on JENKINS-40294 Re: Exec Failure: HTTP:404. Message:Not Found I'm having an exact same issue on a K8N cluster configured on bare metal. Tried configuring a custom logger on org.apache.http to capture the calls but it's not showing any entries. Were you able to figure out a solution to this problem? Thanks! Val 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
Jean Neveux commented on JENKINS-40294
Re: Exec Failure: HTTP:404. Message:Not Found
I'm having the same exception with Kubernet version:
Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.4", GitCommit:"3b417cc4ccd1b8f38ff9ec96bb50a81ca0ea9d56", GitTreeState:"clean", BuildDate:"2016-10-21T02:48:38Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.4", GitCommit:"3b417cc4ccd1b8f38ff9ec96bb50a81ca0ea9d56", GitTreeState:"clean", BuildDate:"2016-10-21T02:42:39Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
And I'm also having another exception at the end of the script:
io.fabric8.kubernetes.client.KubernetesClientException: Not Found
at io.fabric8.kubernetes.client.dsl.internal.ExecWebSocketListener.onFailure(ExecWebSocketListener.java:159)
at com.squareup.okhttp.ws.WebSocketCall$1.onResponse(WebSocketCall.java:100)
at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:177)
at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)
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)
Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
Daniel Serodio created an issue
Jenkins / JENKINS-40294
Exec Failure: HTTP:404. Message:Not Found
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
jenkins-kubernetes.log
Components:
kubernetes-plugin
Created:
2016/Dec/07 8:51 PM
Environment:
Jenkins 2.35, Kubernetes Plugin 0.9, Minikube 0.13.1
Labels:
kubernetes
Priority:
Minor
Reporter:
Daniel Serodio
I'm trying to run a simple pipeline based on the example on the README:
podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave', args: '${computer.jnlpmac} ${computer.name}'),
]) {
node ('mypod') {
stage 'Get a Maven project'
git 'https://github.com/jenkinsci/kubernetes-plugin.git'
container('maven') {
stage 'Build a Maven project'
sh 'mvn clean install'
}
}
}
The pod is created and started, but when Jenkins tries to run the shell script for the build, I get:
