[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2018-04-01 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 should have been fixed by JENKINS-47501  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38260  
 
 
  Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2017-03-29 Thread stokr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomasz Bienkowski commented on  JENKINS-38260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
 I don't know how the fabricat8's Kubernetes client works, but looking at the source code of "addProvisionedSlave" method here: https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-0.10/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java I was wandering if this could be a racing condition. Perhaps fabricat8's client does not return any pod until it is actually ready (started). If so, this might explain why  the Container Capacity is not respected. The sequence of events could be like this: 
 
Jenkins wants to create a slave pod. Container capacity is not exceeded. 
The pod is being deployed to Kubernetes (it is starting). 
Jenkins wants to create another pod, it asks the fabricat8's client if there are any slave pods running. 
fabricat8's client responds that there are no pods (because the pod from step (2) is still being deployed (it is not running yet)). 
Jenkins creates another pod, effectively exceeding Container Capacity setting. 
 Is this reasonable?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed 

[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2017-03-17 Thread stokr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomasz Bienkowski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38260  
 
 
  Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
Change By: 
 Tomasz Bienkowski  
 
 
Attachment: 
 jenkins-master.log  
 

  
 
 
 
 

 
 
 

 
 
 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-38260) Kubernetes plugin does not respect Container Cap

2017-03-17 Thread stokr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomasz Bienkowski commented on  JENKINS-38260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
 Hello, I have the same problem, although in my case it's version 
 
2.32.1 of Jenkins, 
0.10 of the plugin 
 I have attached the log from the Jenkins master instance.  Thanks in advance for any help. jenkins-master.log  
 

  
 
 
 
 

 
 
 

 
 
 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-38260) Kubernetes plugin does not respect Container Cap

2016-12-02 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez commented on  JENKINS-38260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
 without more details (logs) I can't really figure out what you mean. The instance cap is honored in multiple examples   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2016-10-25 Thread jrog...@socialserve.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Rogers commented on  JENKINS-38260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
 BTW, I have switched to Kubernetes CI Plugin. That plugin requires a bit more knowledge about Kubernetes but is more flexible and behaves more correctly in my experience. Specifically, it better respects configured concurrent container count.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2016-10-25 Thread albertv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Albert V updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38260  
 
 
  Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
Change By: 
 Albert V  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2016-10-04 Thread albertv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Albert V updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38260  
 
 
  Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
Change By: 
 Albert V  
 

  
 
 
 
 

 
 The Kubernetes plugin frequently creates more concurrent slaves than the number set in the "Container Cap" field. Even doesn't respect the Max number of instances in the Pod Template field.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap

2016-09-15 Thread jrog...@socialserve.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Rogers created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38260  
 
 
  Kubernetes plugin does not respect Container Cap   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2016/Sep/15 10:17 PM  
 
 
Environment: 
 Jenkins 2.7.1  Kubernetes plugin 0.8  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Rogers  
 

  
 
 
 
 

 
 The Kubernetes plugin frequently creates more concurrent slaves than the number set in the "Container Cap" field.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment