[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden commented on JENKINS-61788 Re: jclouds single-use slave never cleaned up Thanks for the quick fix. I'll try to get a look at this as soon as I can. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205628.1585853221000.9684.1586782740391%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden created an issue Jenkins / JENKINS-61788 jclouds single-use slave never cleaned up Issue Type: Improvement Assignee: Fritz Elfert Components: jclouds-plugin Created: 2020-04-02 18:47 Environment: Jenkins 2.229 jclouds plugin 2.17 Priority: Minor Reporter: Major Hayden When I use the jclouds plugin to spawn instances at DigitalOcean and EC2, I noticed that the single-use slaves are never removed. They are marked offline as soon as the job finishes, but they remain offline in Jenkins and they are active with the cloud provider. As soon as the job finishes, I see this in the logs: 2020-04-02 18:30:42.634+ [id=3070] WARNING j.p.j.c.JCloudsOneOffSlave$JCloudsOneOffSlaveDisposer#tearDown: Taking single-use slave [COMPUTER_NAME] offline. I let it sit for two hours and nothing changed. I had to delete the agent manually from inside Jenkins' build executors listing. Am I missing a step? I'll gladly turn on more debug logging if that would help diagnose the issue.
[JIRA] (JENKINS-53612) Kubernetes plugin keeps trying to build when quota reached
Title: Message Title Major Hayden created an issue Jenkins / JENKINS-53612 Kubernetes plugin keeps trying to build when quota reached Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-17 12:33 Environment: Jenkins 2.121.3 kubernetes 1.12.6 Priority: Minor Reporter: Major Hayden We use Jenkins to build containers in OpenShift (which offers a kubernetes API). However, we found that the Kubernetes plugin doesn't handle quota limits well. It keeps trying over and over again to build new containers without checking to see if the quota limit has been reached. io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://172.56.0.1/api/v1/namespaces/myproject/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods "mycontainer" is forbidden: exceeded quota: myproject-quota, requested: limits.cpu=8, used: limits.cpu=64, limited: limits.cpu=64. I would like to see the plugin do something like this: Plugin checks the current quota usage If the quota has been reached, sleep for a configurable amount of time Check the quota again Repeat steps 2 an
