[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Michael FIG commented on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? Running a "Reload Configuration from Disk" fixed the problem for me. Thanks, Michael. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Carlos Sanchez resolved as Fixed There is a follow up issue at JENKINS-50268 about the empty labels Jenkins / JENKINS-43235 Total container cap of 10 reached when NO slaves are running? Change By: Carlos Sanchez Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title
Michael FIG edited a comment on JENKINS-43235
Re: Total container cap of 10 reached when NO slaves are running?
I'm getting (in Kubernetes Plugin v1.5.2):{{Total container cap of 10 reached, not provisioning: 10 running or errored in namespace default with Kubernetes labels \{}}} {{}} even though I have labels set in the pod template as:{{Labels: good-pika-jenkins-slave}}This is an installation that was performed by the stable/jenkins helm chart, then I upgraded the plugins within it.Are there any tricks to setting the labels?Thanks,Michael.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title
Michael FIG reopened an issue
I'm getting (in Kubernetes Plugin v1.5.2): Total container cap of 10 reached, not provisioning: 10 running or errored in namespace default with Kubernetes labels {}{{}} even though I have labels set in the pod template as: Labels: good-pika-jenkins-slave This is an installation that was performed by the stable/jenkins helm chart, then I upgraded the plugins within it. Are there any tricks to setting the labels? Thanks, Michael.
Jenkins / JENKINS-43235
Total container cap of 10 reached when NO slaves are running?
Change By:
Michael FIG
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Mark Schroering commented on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? I'm hitting the same thing. kubectl get po -l jenkins=slave shows 0 pods, but kubectl describe pods -l jenkins=slave does return all of my previous past/failed jobs. Looking at the plugin code, it looks like this is what it may be doing to pull in the pods. Maybe a status check for only running pods should be used? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck commented on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? Here is a senario. I have cap conf at 20.. it does not start.. i increase to 100 and then is says Waiting for Pod to be scheduled (0/100). If there was 20 running it should say 20/100? Mar 31, 2017 11:38:50 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 20 reached, not provisioning: 20 running in namespace default Mar 31, 2017 11:39:00 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 31, 2017 11:39:00 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 20 reached, not provisioning: 20 running in namespace default Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 31, 2017 11:39:10 AM io.fabric8.kubernetes.client.Config tryServiceAccount WARNING: Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring. Mar 31, 2017 11:39:10 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes-dev with 1 executors. Remaining excess workload: 0 Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Created Pod: deploy-kubernetes-4df2b007ba2f Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Waiting for Pod to be scheduled (0/100): deploy-kubernetes-4df2b007ba2f Mar 31, 2017 11:39:13 AM hudson.TcpSlaveAgentListener$ConnectionHandler run Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck edited a comment on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? kubectl get po -l jenkins=slave shows 0 pods. https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java#L743So that code should not give 20? Its worth noting that i have 2 jenkins masters deploying creating slaves. And my old one have also started complaining about total cap reached. So i created a new namespace and configured my second master to use that and now the problem is gone. But the code seems to only count labels jenkins:slave so it should not be a problem? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck commented on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? kubectl get po -l jenkins=slave shows 0 pods. https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java#L743 So that code should not give 20? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck updated an issue Jenkins / JENKINS-43235 Total container cap of 10 reached when NO slaves are running? Change By: Jonas Falck Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck created an issue Jenkins / JENKINS-43235 Total container cap of 10 reached when NO slaves are running? Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Mar/30 3:03 PM Priority: Minor Reporter: Jonas Falck I have currently 39 pods running in the cluster default namespace. None of them are created by jenkins.plugins.kubernetes. If i increase limit to for example 50 it starts to create slaves. But why does it count more than i should? Mar 30, 2017 4:54:50 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default Mar 30, 2017 4:55:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 30, 2017 4:55:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default Mar 30, 2017 4:55:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 30, 2017 4:55:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default Mar 30, 2017 4:55:20 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 30, 2017 4:55:20 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave running a new installatin of jenkins 2.46.1 and kubernetes plugin 0.11
