[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez updated JENKINS-56347 Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197933.1551459214000.19693.1557231721464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title
Dax Games edited a comment on JENKINS-56347
Re: Kubernetes plugin provisioning pods twice in 1.14.6
No problem, just trying to help.That fixes it!{code:java}May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider createClientINFO: Created new Kubernetes client: kubernetes io.fabric8.kubernetes.client.DefaultKubernetesClient@5339d085May 02, 2019 1:18:54 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?May 02, 2019 1:18:54 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0May 02, 2019 1:19:04 PM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)May 02, 2019 1:19:04 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: pd-pipedream/pd-slave-g6cwhMay 02, 2019 1:19:04 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Pod is running: pd-pipedream/pd-slave-g6cwhMay 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (0/250): pd-slave-g6cwhMay 02, 2019 1:19:08 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (1/250): pd-slave-g6cwhMay 02, 2019 1:19:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (2/250): pd-slave-g6cwh{code} Any idea how long before a new version is released?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 No problem, just trying to help. That fixes it! May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label pd-slave: Kubernetes Pod Template May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider createClient INFO: Created new Kubernetes client: kubernetes io.fabric8.kubernetes.client.DefaultKubernetesClient@5339d085 May 02, 2019 1:18:54 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 02, 2019 1:18:54 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 02, 2019 1:19:04 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) May 02, 2019 1:19:04 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: pd-pipedream/pd-slave-g6cwh May 02, 2019 1:19:04 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: pd-pipedream/pd-slave-g6cwh May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (0/250): pd-slave-g6cwh May 02, 2019 1:19:08 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (1/250): pd-slave-g6cwh May 02, 2019 1:19:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (2/250): pd-slave-g6cwh Add Comment
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 thanks for the diagnosis, that seems to be the cause. I have updated the PR at https://github.com/jenkinsci/kubernetes-plugin/pull/455 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez updated JENKINS-56347 Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Carlos Sanchez Status: In Progress Review 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 The [ commit |[ that introduced this issue? https://github.com/jenkinsci/kubernetes-plugin/commit/30488eea66dd773ce57f18d1b79a7410affa476a#diff-d31a23c33d2739a785384f53a13bc682 ]] that introduced this? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 The [commit|[https://github.com/jenkinsci/kubernetes-plugin/commit/30488eea66dd773ce57f18d1b79a7410affa476a#diff-d31a23c33d2739a785384f53a13bc682]] that introduced this? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 The [commit|[https://github.com/jenkinsci/kubernetes-plugin/commit/30488eea66dd773ce57f18d1b79a7410affa476a#diff-d31a23c33d2739a785384f53a13bc682]] that introduced this? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 The commit that introduced this? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 It looks like there needs to be a wait for a connect back to Jenkins [here|https://github.com/jenkinsci/kubernetes-plugin/blob/b9ea4ffc59e8447671002189e91f343919fba668/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L120-L125]Like the working code [here| [ https://github.com/jenkinsci/kubernetes-plugin/blob/b4fd88b12ad461efe7cc49fa58c0ef2d14dc2053/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L180-L238] .] But I am certainly no Java expert. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 It looks like there needs to be a wait for a connect back to Jenkins here Like the working code here But I am certainly no Java expert. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 It looks like the plugin is only waiting for the pod to be running and not waiting for it to actually connect back to jenkins. The working plugin waits for the pod to connect back to Jenkins. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title
Dax Games edited a comment on JENKINS-56347
Re: Kubernetes plugin provisioning pods twice in 1.14.6
As a comparison this is from 1.14.5 plugin: {code:java}May 01, 2019 2:36:14 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 01, 2019 2:36:14 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 01, 2019 2:36:14 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?May 01, 2019 2:36:14 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0May 01, 2019 2:36:24 PM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)May 01, 2019 2:36:24 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: pd-slave-12gpw in namespace pd-pipedreamMay 01, 2019 2:36:24 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for Pod to be scheduled (0/600): pd-slave-12gpwMay 01, 2019 2:36:25 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Container is waiting pd-slave-12gpw [jnlp]: ContainerStateWaiting(message=null, reason=ContainerCreating, additionalProperties={})May 01, 2019 2:36:25 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for Pod to be scheduled (1/600): pd-slave-12gpwMay 01, 2019 2:36:26 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (0/250): pd-slave-12gpwMay 01, 2019 2:36:27 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (1/250): pd-slave-12gpwMay 01, 2019 2:36:28 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (2/250): pd-slave-12gpwMay 01, 2019 2:36:29 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (3/250): pd-slave-12gpwMay 01, 2019 2:36:30 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (4/250): pd-slave-12gpwMay 01, 2019 2:36:31 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (5/250): pd-slave-12gpwMay 01, 2019 2:36:32 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (6/250): pd-slave-12gpwMay 01, 2019 2:36:33 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (7/250): pd-slave-12gpwMay 01, 2019 2:36:34 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (8/250): pd-slave-12gpwMay 01, 2019 2:36:35 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (9/250): pd-slave-12gpwMay 01, 2019 2:36:36 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (10/250): pd-slave-12gpwMay 01, 2019 2:36:37 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (11/250): pd-slave-12gpwMay 01, 2019 2:36:38 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (12/250): pd-slave-12gpwMay 01, 2019 2:36:39 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (13/250):
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title
Dax Games commented on JENKINS-56347
Re: Kubernetes plugin provisioning pods twice in 1.14.6
As a comparison this is from 1.14.5 plugin:
May 01, 2019 2:36:14 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Kubernetes agents: 1
May 01, 2019 2:36:14 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Template for label pd-slave: Kubernetes Pod Template
May 01, 2019 2:36:14 PM okhttp3.internal.platform.Platform log
INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?
May 01, 2019 2:36:14 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0
May 01, 2019 2:36:24 PM hudson.slaves.NodeProvisioner$2 run
INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)
May 01, 2019 2:36:24 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Created Pod: pd-slave-12gpw in namespace pd-pipedream
May 01, 2019 2:36:24 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (0/600): pd-slave-12gpw
May 01, 2019 2:36:25 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Container is waiting pd-slave-12gpw [jnlp]: ContainerStateWaiting(message=null, reason=ContainerCreating, additionalProperties={})
May 01, 2019 2:36:25 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for Pod to be scheduled (1/600): pd-slave-12gpw
May 01, 2019 2:36:26 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (0/250): pd-slave-12gpw
May 01, 2019 2:36:27 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (1/250): pd-slave-12gpw
May 01, 2019 2:36:28 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (2/250): pd-slave-12gpw
May 01, 2019 2:36:29 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (3/250): pd-slave-12gpw
May 01, 2019 2:36:30 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (4/250): pd-slave-12gpw
May 01, 2019 2:36:31 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (5/250): pd-slave-12gpw
May 01, 2019 2:36:32 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (6/250): pd-slave-12gpw
May 01, 2019 2:36:33 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (7/250): pd-slave-12gpw
May 01, 2019 2:36:34 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (8/250): pd-slave-12gpw
May 01, 2019 2:36:35 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (9/250): pd-slave-12gpw
May 01, 2019 2:36:36 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (10/250): pd-slave-12gpw
May 01, 2019 2:36:37 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch
INFO: Waiting for agent to connect (11/250): pd-slave-12gpw
May 01, 2019 2:36:38 PM
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Logs from PR in https://github.com/jenkinsci/kubernetes-plugin/pull/455. This is a build of a single job that spins up 8 slaves: May 01, 2019 2:13:50 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 May 01, 2019 2:13:50 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label pd-slave: Kubernetes Pod Template May 01, 2019 2:13:50 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 01, 2019 2:13:50 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 01, 2019 2:14:00 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) May 01, 2019 2:14:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: pd-compute-platform/pd-slave-zcf1g May 01, 2019 2:14:00 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 01, 2019 2:14:02 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: pd-compute-platform/pd-slave-zcf1g May 01, 2019 2:14:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 May 01, 2019 2:14:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label pd-slave: Kubernetes Pod Template May 01, 2019 2:14:10 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 01, 2019 2:14:20 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s) May 01, 2019 2:14:20 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: pd-compute-platform/pd-slave-txmw8 May 01, 2019 2:14:20 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 01, 2019 2:14:21 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: pd-compute-platform/pd-slave-txmw8 May 01, 2019 2:14:30 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 May 01, 2019 2:14:30 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label pd-slave: Kubernetes Pod Template May 01, 2019 2:14:30 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 01, 2019 2:14:40 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 4 computer(s) May 01, 2019 2:14:40 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: pd-compute-platform/pd-slave-61lwt May 01, 2019 2:14:40 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Same issue here on 1.15.1 and 1.15.2 will see if I can try the PR and report back. I am seeing a slave spin every 10 seconds until one connects. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Same issue here on 1.15.1 and 1.15.2 will see if I can try the PR and report back. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez started work on JENKINS-56347 Change By: Carlos Sanchez Status: Open In Progress 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Can you try the PR in https://github.com/jenkinsci/kubernetes-plugin/pull/455 and post the logs ? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Raúl Cruz commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We have the same problem here, it started to happend once we added this: https://github.com/jenkinsci/kubernetes-plugin/#over-provisioning-flags Then we removed the flags but it was still happening, so we downgraded to 1.14.5 and now is not happening. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Stephan Pauxberger commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Same here, downgrading to 1.14.5 solved it for now. Did not yet get around to setting up a test system. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Sriniva Pothala edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We are seeing the same problem as well in version 1.14.8 but it was intermittent. I am unable to reproduce it when its not happening. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Sriniva Pothala commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We are seeing the same problem as well in version 1.14.8 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Christian Tryti commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Not in that jenkins-instance. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 what I see in the logs is that the KubernetesCloud.provision is called 3 times, something that is controlled by Jenkins, not the plugin. Although it's suspicious that both of you say started happening in 1.14.6 Do you have the settings in https://github.com/jenkinsci/kubernetes-plugin/#over-provisioning-flags ? 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Christian Tryti commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 I can leave that jenkins-instance running, in case you want more logs. Shout out if you need more details about the rest of the setup as well. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Christian Tryti commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Recreated it on Jenkins 2.150.3 with the following plugins (that i think might have any relevance): Kubernetes-plugin: 1.14.8 Kubernetes-pipeline-plugin: 1.6 Kubernetes-credentials: 0.4.0 Our jobs run declarative pipelines. The following log jenkins.log shows 3 slaves being created. With kubernetes-plugin 1.14.5, only 1 slave is created for each job. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Christian Tryti updated an issue Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Christian Tryti Attachment: jenkins.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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Christian Tryti commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We had the same problem with 1.14.6 and 1.14.8. Each job we ran created one slave, then a second 20 seconds later. This quickly drained the available resources in our namespace. We also avoided the problem by rolling back to 1.14.5. Unfortunately we don't have any logs of it right now. But I'll try to find time to reproduce it and get some logs. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 there's nobody else experiencing that behavior, so unless you can provide definitions, debug logs,... there's not much that can be done 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Filip Pytloun commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 Any update? This is serious issue and is also affecting latest version 1.14.8. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Filip Pytloun updated an issue Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Filip Pytloun Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after.I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0).Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent:Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed. 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Filip Pytloun created an issue Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-01 16:53 Priority: Major Reporter: Filip Pytloun Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after. I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0). Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent: Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed. Add Comment
