[JIRA] (JENKINS-53621) Executors in-progress block container provisioning after configuration changes

[r...@akom.net (JIRA)]

Title: Message Title

Alexander Komarov created an issue   Jenkins / JENKINS-53621 Executors in-progress block container provisioning after configuration changes Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-09-17 14:27 Environment: CentOS 6.8, Jenkins 2.141 Docker-Plugin 1.1.5 Priority: Minor Reporter: Alexander Komarov Changing Cloud configuration while there are existing containers seems to really screw things up.  I changed the docker host URI (to a different host) and changed the Container Cap. As a result, on the new host, I had a disagreement between the Container Cap and the actual container count.  For example, I had the following combination at one point: Containers running: 1 Container Cap: 7 (I kept increasing it, but it only helped temporarily) Log shows:  Sep 17, 2018 7:16:35 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision Not provisioning additional slaves for container&&centos&&mem32; we have 3 executors being started already This did not change in 3 days (Jenkins just kept printing this in the log), so I hacked my way into clearing the count of containers in progress in a jenkins script console: (I have only one Docker cloud) Jenkins.getInstance().clouds.get(com.nirima.jenkins.plugins.docker.DockerCloud).CONTAINERS_IN_PROGRESS.clear() And now I'm getting the right count of provisioned containers!   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.