[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted yes, that fix should work in all cases 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Carlos Sanchez Thanks for this information. I will try it as soon as the pull builds successfull. So with this fix in place, pod template out of pipeline can still be used? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted see https://github.com/jenkinsci/kubernetes-plugin/pull/388 for a proper fix 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted No its only this one. I will try to do some try and error testing to get the variable somehow into the pod. Will update as soon as i have news 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted No its only this one. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted do you have more pod templates defined and is picking a different one ? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori updated an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Change By: leon gregori Attachment: image-2018-10-22-09-47-09-082.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Okay, i named it jnlp, only 1 container is created now. But im still missing the variable pod_name $ kubectl describe pod test-2jrwj Name: test-2jrwj Namespace: default Priority: 0 PriorityClassName: Node: 10.144.180.238/10.144.180.238 Start Time: Mon, 22 Oct 2018 09:44:34 +0200 Labels: jenkins=slave jenkins/test=true Annotations:kubernetes.io/psp=ibm-privileged-psp Status: Running IP: 172.30.202.66 Containers: jnlp: Container ID: containerd://60f5b2ad8849852ac09e5afb018d6b625a25710e9618b4d20910387eb763d7c7 Image: jenkinsci/jnlp-slave Image ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aa Port: Host Port: Command: /bin/sh -c Args: cat State: Running Started: Mon, 22 Oct 2018 09:44:36 +0200 Ready: True Restart Count: 0 Environment: JENKINS_SECRET: 46c5400d9757f360eeb132758bee5ea444954d558bb8543cd715e09c21a180c9 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-2jrwj JENKINS_NAME:test-2jrwj JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkins Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: workspace-volume: Type:EmptyDir (a temporary directory that shares a pod's lifetime) Medium: default-token-9hntr: Type:Secret (a volume populated by a Secret) SecretName: default-token-9hntr Optional:false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: TypeReason Age From Message -- --- Normal Scheduled 22s default-schedulerSuccessfully assigned default/test-2jrwj to 10.144.180.238 Normal Pulled 21s kubelet, 10.144.180.238 Container image "jenkinsci/jnlp-slave" already present on machine Normal Created21s kubelet, 10.144.180.238 Created container Normal Started20s kubelet, 10.144.180.238 Started container Definition:
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[~csanchez] I used the yaml syntax now for "jenkins-slave" jnlp container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins yaml is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job.Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave.EDIT used properly : I just saw that i added a whole new yaml into the yaml section which is then merged with the default one. {code:java} Containers: jenkins !image - slave:Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9bImage: jenkinsci/jnlp-slaveImage ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aaPort: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200Ready: FalseRestart Count: 0Environment: JENKINS_URL: http://my - release 10 - jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name)Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp:Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9Image: jenkins/jnlp-slave:alpineImage ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185edPort: Host Port: State: Running Started: Mon, 22 Oct 2018 - 09 :11:07 +0200Ready: TrueRestart Count: 0Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my - release 40 - jenkins 49 - agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkinsMounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes 930 . io/serviceaccount from default-token-9hntr (ro)Conditions:{code}{code:java}### CONTAINER 1 (jnlp)$ kubectl logs test-bpqmd jnlpWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: test-bpqmdOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.26Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://my-release-jenkins:8080/]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted don't name the container jenkins-slave, name it jnlp 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[~csanchez] I used the yaml syntax now for "jenkins-slave" container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job.Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave. EDIT: I just saw that i added a whole new yaml into the yaml section which is then merged with the default one. {code:java}Containers: jenkins-slave:Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9bImage: jenkinsci/jnlp-slaveImage ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aaPort: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200Ready: FalseRestart Count: 0Environment: JENKINS_URL: http://my-release-jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name)Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp:Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9Image: jenkins/jnlp-slave:alpineImage ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185edPort: Host Port: State: Running Started: Mon, 22 Oct 2018 09:11:07 +0200Ready: TrueRestart Count: 0Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkinsMounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro)Conditions:{code}{code:java}### CONTAINER 1 (jnlp)$ kubectl logs test-bpqmd jnlpWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: test-bpqmdOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.26Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://my-release-jenkins:8080/]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Carlos Sanchez I used the yaml syntax now for "jenkins-slave" container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job. Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave. Containers: jenkins-slave: Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9b Image: jenkinsci/jnlp-slave Image ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aa Port: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200 Ready: False Restart Count: 0 Environment: JENKINS_URL: http://my-release-jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name) Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp: Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9 Image: jenkins/jnlp-slave:alpine Image ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185ed Port: Host Port: State: Running Started: Mon, 22 Oct 2018 09:11:07 +0200 Ready: True Restart Count: 0 Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkins Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) Conditions: ### CONTAINER 1 (jnlp) $ kubectl logs test-bpqmd jnlp Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Oct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: test-bpqmd Oct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.26 Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Oct 22, 2018 7:16:18 AM
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted you would need to use the yaml syntax, I don't think valuefrom will work 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Im currently fighting with the pod template definition. The variable is available in the pod but empty / not defined, need some more try and error until i make it i guess.
// Simple Jenkinsfile for testing Kubernetes Plugin
// Developers input is required here.
def appname = "AddressManagement"
def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentials
def cloud = env.CLOUD ?: "kubernetes"
def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"
def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"
def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"
def serviceAccount = env.SERVICE_ACCOUNT ?: "default"
def sonarCredsID = "sonarID"
appname = appname.toLowerCase()// Pod Environment Variables
def kubenamespace = "default"
def regnamespace = "blw-msa"
def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [
envVar(key: 'NAMESPACE', value: kubenamespace),
envVar(key: 'REGNAMESPACE', value: regnamespace),
envVar(key: 'JARNAME', value: jarname),
envVar(key: 'APPNAME', value: appname),
envVar(key: 'POD_NAME', valuefrom: { fieldref: { fieldPath: metadata.name }}),
envVar(key: 'REGISTRY', value: registry)
],
volumes: [
//hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'),
//hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')
//hostPathVolume(hostPath: '/tmp/gradle', mountPath: '/root/.gradle/caches/')
],
containers: [
// In Theory, java container is not needed as the normal jenkins jnlp slave would be capable of executing gradle.
// But as we mount the cache from host, we need a root user running inside the build container, otherwise gradle wont be able to write to .gradle
containerTemplate(name: 'java', image: 'openjdk:8-jdk', ttyEnabled: true, command: 'cat')
]) {node('mypod') {
stage('Checkout') {
echo "test"
}
container('java') {
stage('Static Code Analysis') {
sh "java -version"}
}
}
}
$ kubectl get pod jenkins-slave-hcwsg-c9ntw -o yaml
apiVersion: v1
kind: Pod
metadata:
annotations:
kubernetes.io/psp: ibm-privileged-psp
creationTimestamp: 2018-10-19T11:11:45Z
deletionGracePeriodSeconds: 30
deletionTimestamp: 2018-10-19T11:12:28Z
labels:
jenkins: slave
jenkins/mypod: "true"
name: jenkins-slave-hcwsg-c9ntw
namespace: default
resourceVersion: "20068"
selfLink: /api/v1/namespaces/default/pods/jenkins-slave-hcwsg-c9ntw
uid: c3ad40dc-d38f-11e8-a534-0623e2fdc71b
spec:
containers:
- command:
- cat
env:
- name: NAMESPACE
value: default
- name: JENKINS_SECRET
value: 0e822b8d1bc6da327721f803279853438234f3e6076279b600a219d732e0555f
- name: JENKINS_TUNNEL
value: my-release-jenkins-agent:5
- name: JENKINS_AGENT_NAME
value: jenkins-slave-hcwsg-c9ntw
- name: REGNAMESPACE
value: blw-msa
- name: JARNAME
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted The plugin gets the pod name from the /etc/hostname file and looks like IKS just sets hostname to localhost instead of the pod name https://github.com/jenkinsci/kubernetes-plugin/blob/2e10cd29fa7bd1bca86e3716f04af61af818639e/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/KubernetesNodeContext.java#L42 Only solution I can think of is the use of the downward API https://stackoverflow.com/questions/37253068/programmatically-get-the-name-of-the-pod-that-a-container-belongs-to-in-kubernet/37261036 Please try with the latest commit in the branch and adding this to your pod definition env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Carlos Sanchez I tested the JENKINS-53297 plugin Manage Plugins: Kubernetes plugin This plugin integrates Jenkins with Kubernetes 1.12.10-SNAPSHOT (private-d0dc3394-blwdev) I tested your Commit with the following Jenkinsfile:
// Simple Jenkinsfile for testing Kubernetes Plugin
// Developers input is required here.
def appname = "AddressManagement"
def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentials
def cloud = env.CLOUD ?: "kubernetes"
def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"
def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"
def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"
def serviceAccount = env.SERVICE_ACCOUNT ?: "default"
def sonarCredsID = "sonarID"
appname = appname.toLowerCase()
// Pod Environment Variables
def kubenamespace = "default"
def regnamespace = "blw-msa"
def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [
envVar(key: 'NAMESPACE', value: kubenamespace),
envVar(key: 'REGNAMESPACE', value: regnamespace),
envVar(key: 'JARNAME', value: jarname),
envVar(key: 'APPNAME', value: appname),
envVar(key: 'REGISTRY', value: registry)
],
volumes: [
//hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'),
//hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')
//hostPathVolume(hostPath: '/tmp/gradle', mountPath: '/root/.gradle/caches/')
],
containers: [
containerTemplate(name: 'java', image: 'openjdk:8-jdk', ttyEnabled: true, command: 'cat')
]) {node('mypod') {
stage('Checkout') {
echo "test"
}
container('java') {
stage('Static Code Analysis') {
sh "java -version"}
}
}
}
This unfortunately has not helped, the issue is still the same (Providing Console Output of above Jenkinsfile) :
Started by user admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Agent jenkins-slave-brxph-v8fff is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (mypod):
* [java] openjdk:8-jdkRunning on jenkins-slave-brxph-v8fff in /home/jenkins/workspace/testingSimple
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] echo
test
[Pipeline] }
[Pipeline] // stage
[Pipeline] container
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Static Code Analysis)[Pipeline] sh
[testingSimple] Running shell script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.waitUntilExists(BaseOperation.java:959)
at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted @Carlos Sanchez will try tomorrow . Appreciate your commits 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted @Carlos Sanchez will try tomorrow 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Can you try building the JENKINS-53297 branch in PR-385 and see what is the error now? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
So i can only say that the issue in this ticket was now reproduced by me:(IKS 1.11, Plugin 1.12.4 or 1.12.9, happens on both){code:java}[testingSimple] Running shell script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of Pipelinejava.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.waitUntilExists(BaseOperation.java:959) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:219) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:37) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:417) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:185) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:98) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:264) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor142.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)Caused: java.io.IOException: Failed to execute shell script inside container [java] of pod [localhost]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:438) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted [~dcurrie] IBM container registry "cr build" command uses local docker deamon. I just tried it and it build locally.So i think there are only 2 workarounds:1. Having docker build Slave on some VM outside of K82. Using some Java based building service like kaniko See also [https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
So i can only say that the issue in this ticket was now reproduced by me:(IKS 1.11, Plugin 1.12.4 or 1.12.9, happens on both){code:java} [ testingSimple] Running shell script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of Pipelinejava.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.waitUntilExists(BaseOperation.java:959) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:219) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:37) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:417) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:185) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:98) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:264) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor142.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)Caused: java.io.IOException: Failed to execute shell script inside container [java] of pod [localhost]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:438) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[ https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199 ] I will evaluate now if IKS 1.11 supports all other operations :Update Edit:{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199]I will evaluate now if IKS 1.11 supports all other operations:Update Edit:{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color} {color:#00}Seems like even if you find a workaround for docker in docker, now the problem is that with this plugin no sh can be executed inside new containers{color}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori updated an issue
Jenkins / JENKINS-53297
Kubernetes v1.11 - ChannelClosed after job delaying aborted
Change By:
leon gregori
Comment:
{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted [ https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199 ] I will evaluate now if IKS 1.11 supports all other operations 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted [ https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199 ]I will evaluate now if IKS 1.11 supports all other operations 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted David Currie IBM container registry "cr build" command uses local docker deamon. I just tried it and it build locally. So i think there are only 2 workarounds: 1. Having docker build Slave on some VM outside of K8 2. Using some Java based building service like kaniko 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title David Currie commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted You can't expect to be able to just swap out the Docker socket for a containerd socket and have that work. Even setting that aside, containerd doesn't even have the concept of building images. I've been out of the loop a bit with IKS but I suspect the path of least resistance here is to have Jenkins use the IBM Container Registry to build your Docker images i.e. via ibmcloud cr build. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted docker-sock-volume: Type: HostPath (bare host directory volume) Path: /var/run/containerd/containerd.sock HostPathType: File Seems to work. So within a docker container from pipeline this can be mounted to execute eg. "docker build ." But it gives new error Error: failed to create containerd task: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"docker pull jenkins\": executable file not found in $PATH": unknown Warning BackOff 0s (x2 over 2s) kubelet, 10.144.181.244 Back-off restarting failed container 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted I'll need to get back on this. Will need to spin up a new cluster in 1.11 to test again tomorrow. Could just have been the bad mount. Thanks very much for the leads ! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the \ { { hostPathVolume} } from the \ { { podTemplate} } ? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the {hostPathVolume} from the {podTemplate}? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie updated an issue
Jenkins / JENKINS-53297
Kubernetes v1.11 - ChannelClosed after job delaying aborted
Change By:
David Currie
I've Jenkins running on Kubernetes Cluster (Bluemix IKS).I am using the kubernetes plugin to create dynamic agents.The jenkins connection with agent is made in the standard way: - Jenkins URL: jenkins:8080- Jenkins Tunnel: jenkins-agent:5 When i start a job, the agent connect with Jenkins master successfully. But he keeps long time and not execute pipeline steps. Agent logs: {code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorAug 29, 2018 12:07:02 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins-slave-n39mq-9zgzzAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.23Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://jenkins:8080/]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-agent Agent port: 5 Identity: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-agent:5Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: ConnectedAug 29, 2018 12:12:09 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave$SlaveDisconnector callINFO: Disabled slave engine reconnects.Aug 29, 2018 12:12:09 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: hudson.remoting.ChannelClosedException: Channel "unknown": Protocol stack cannot write data anymore. ChannelApplicationLayer reports that the NIO Channel is closed at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1038) at hudson.remoting.Channel.close(Channel.java:1439)
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hi David, About the docker builds I was thinking on the same grounds. But, before we reach that step the issue is the builder containers spawned up for the job itself is the issue. Currently, jenkins master doesn't see the slave builder container ready status. My error is `Timed out waiting for container to become ready!` Is the Kubernetes Pod Template, using docker daemon underneath? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title David Currie commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Is that Jenkinsfile just an example or what you're actually trying to achieve? You shouldn't need a Docker socket in order to use helm. That is not to say that this isn't a problem in other scenarios e.g. when trying to use the daemon on the Kubernetes node to perform Docker builds. In that case, you could look at using kaniko or fall back to Docker-in-Docker. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Still no solution until now. 1.11 Kubernetes on IBM Cloud uses containerd runtime and we dont know how to use the correct socket. I think same is applicable for kubernetes plugin in jenkins. See also: https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd?noredirect=1#comment92152693_52179148 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori updated an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Change By: leon gregori Environment: Jenkins 2.121.3 , 2.141 Kubernetes IKS 1.11 (Bluemix)Kubernetes Plugin 1.12.4 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Alok Rajiv yes that is the root cause if using IKS 1.11. In Jenkins Pipeline it should be just fine to mount containerd socket instead of docker socket. I could not yet test this as our cluster is not updated yet to containerd. I will keep you updated here. Currently (Working on old IBM IKS) volumes: [ hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'), hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')] Possible fix (Working on new containerd IBM IKS) volumes: [ hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: 'Certificates'), hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: 'SOCKET FOR CONTAINERD')] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hi ,So, I think what everyone is facing here is an issue stemming from the runtime dependency change. Thanks to @rtheis from IBM Cloud Network Dev Team on Slack who reminded me of the change.*IKS on K8S v1.11 now uses* +_*containerd*_+ *runtime instead of docker runtime.* I fear this is why our container state cannot be ready by then the master. I experimented on 2 new fresh clusters with 1.10 and 1.11 on IBM Cloud and do confirm that 1.10 works just fine and replicated the above issue on 1.11 (The docker mount itself is failing on 1.11) IBM migration doc link: [https://console.bluemix.net/docs/containers/cs_versions.html#containerd] Do correct me if anyone has another side to this story. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hi ,So, I think what everyone is facing here is an issue stemming from the runtime dependency change. Thanks to @rtheis from IBM Cloud Network Dev Team on Slack who reminded me of the change.*IKS on K8S v1.11 now uses* +_* containerd *_+ *runtime instead of docker runtime.* I fear this is why our container state cannot be ready by then master. I experimented on 2 new fresh clusters with 1.10 and 1.11 on IBM Cloud and do confirm that 1.10 works just fine and replicated the above issue on 1.11 IBM migration doc link: [https://console.bluemix.net/docs/containers/cs_versions.html#containerd] Do correct me if anyone has another side to this story. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hi , So, I think what everyone is facing here is an issue stemming from the runtime dependency change. Thanks to @rtheis from IBM Cloud Network Dev Team on Slack who reminded me of the change. IKS on K8S v1.11 now uses containerd runtime instead of docker runtime. I fear this is why our container state cannot be ready by then master. I experimented on 2 new fresh clusters with 1.10 and 1.11 on IBM Cloud and do confirm that 1.10 works just fine and replicated the above issue on 1.11 IBM migration doc link: https://console.bluemix.net/docs/containers/cs_versions.html#containerd Do correct me if anyone has another side to this story. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Hello, I have also been using the Jenkins Kubernetes Plugin 1.12.4 on IBM Cloud. It also stopped working over the Weekend and im currently in investigation. Job output is this, but i will provide more soon. As soon as I can identify the issue and see if it is another root cause, I will create a seperate issue. {code:java} java.io.IOException: container [java] does not exist in pod [jenkins-slave-sm0j8-666ng] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:435) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:186) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:86) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:182) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor906.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:44) at ___cps __cps . transform___ 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.GeneratedMethodAccessor73.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hello, I have also been using the Jenkins Kubernetes Plugin 1.12.4 on IBM Cloud. It also stopped working over the Weekend and im currently in investigation. Job output is this, but i will provide more soon. As soon as I can identify the issue and see if it is another root cause, I will create a seperate issue. java.io.IOException: container [java] does not exist in pod [jenkins-slave-sm0j8-666ng] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:435) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:186) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:86) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:182) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor906.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:44) 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.GeneratedMethodAccessor73.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Vinicius Xavier commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted I attached a log, from the beginning of the job to the first 404 in the endpoint pods / localhost. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Vinicius Xavier updated an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Change By: Vinicius Xavier Attachment: jenkins-master.log 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
Vinicius Xavier commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
I noticed that when using for example: 'echo hi', the pipeline runs successfully, jenkins GET pods/ endpoint. But, when using any command 'sh "cat /etc/hosts" ', jenkins try GET pods/localhost endpoint
--> GET https://kubernetes.default/api/v1/namespaces/jenkins/pods/localhost http/1.1
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJqZW5raW5zIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6ImplbmtpbnMtdG9rZW4tZnFsZmMiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiamVua2lucyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjM3NzU1YTY1LTk1YmEtMTFlOC04MzlkLTJhZGJhODJkZmMxMSIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpqZW5raW5zOmplbmtpbnMifQ.mfHpadNaF6JhwS7YL171TBg1J_RxOQJwfcyAYUHDjPnc3VI_E6_LwXZ9CRJIIXxtcN7Ny8EWwL09EonaFq20LfZNK5TQaYbu6FIyipMNGaZ1JxA-vPZ-ZYghxOJcbK36JK_ap71g9Jiun7qUVbqGo39yuF6Ga-ELcDil30BOX3FMrZiAH3D6yTy0FUKMLt81KnCzwUEdyKSOO86Z6nNzzZTQ8qw_lVJOJbUPjicbMcOLz1yp19UW8sFYr2smY-BSv6oeHkoXCfbccKu7UsRFSxFKnFOK-5bv8TBwuZm8Wkm93RVUg9dNhrGnYUI5RtzJ1i2ntjqyBSBdYDeinYz5VPPTRhK7zG_k8bmIsw1OAiUdKEQZIsON1EaNYxFEwJ2yd3byQ5N-BUvkfEbOXwM6pWbKDM_RjEfZcFcSXr2XOC_1q6vbwaWBLKtEyD_xvz_ZLq7dbIU5N-FYm8NwAtSYcyxssnHleOqpUfUcDvVepkXJySMs__aarzMjdQYqLhpoCDQtiAZUq6LyFRtW3AezOClj1vweUoUKVx5KCyHm3meEKFc38TUUn9BkYY3lMlz4Q579TLzKzlTmQSFy9sdY1eSvQlikzLx-VSCb5aSc9D6xrINbky0tDmFH1uM7eT7oNRE9ZphctWADz3kZrP_cU-EWW4Ja798jpln93YgrFpY
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Host: kubernetes.default
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Connection: Keep-Alive
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Accept-Encoding: gzip
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
User-Agent: okhttp/3.9.1
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
--> END GET
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
<-- 404 Not Found https://kubernetes.default/api/v1/namespaces/jenkins/pods/localhost (3ms)
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Content-Type: application/json
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Date: Wed, 29 Aug 2018 19:28:34 GMT
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Content-Length: 186
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"localhost\" not found","reason":"NotFound","details":{"name":"localhost","kind":"pods"},"code":404}
Aug 29, 2018 7:28:34 PM INFO okhttp3.internal.platform.Platform log
<-- END HTTP (186-byte body)
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted what are the log lines before that one 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
Vinicius Xavier commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
I actived the ALL log level and caught this:
<-- 404 Not Found https://kubernetes.default/api/v1/namespaces/jenkins/pods/localhost (3ms)Aug 29, 2018 6:32:10 PM INFO okhttp3.internal.platform.Platform logContent-Type: application/jsonAug 29, 2018 6:32:10 PM INFO okhttp3.internal.platform.Platform logDate: Wed, 29 Aug 2018 18:32:10 GMTAug 29, 2018 6:32:10 PM INFO okhttp3.internal.platform.Platform logContent-Length: 186Aug 29, 2018 6:32:10 PM INFO okhttp3.internal.platform.Platform logAug 29, 2018 6:32:10 PM INFO okhttp3.internal.platform.Platform log{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"localhost\" not found","reason":"NotFound","details":{"name":"localhost","kind":"pods"},"code":404}
Why jenkins using 'localhost' with name of the pod???
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Vinicius Xavier created an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-29 00:54 Environment: Jenkins 2.121.3 Kubernetes IKS 1.11 (Bluemix) Kubernetes Plugin 1.12.4 Labels: kubernetes-plugin jenkins Priority: Blocker Reporter: Vinicius Xavier I've Jenkins running on Kubernetes Cluster (Bluemix IKS). I am using the kubernetes plugin to create dynamic agents. The jenkins connection with agent is made in the standard way: Jenkins URL: jenkins:8080 Jenkins Tunnel: jenkins-agent:5 When i start a job, the agent connect with Jenkins master successfully. But he keeps long time and not execute pipeline steps. Agent logs: Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorAug 29, 2018 12:07:02 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up
