[JIRA] [docker-plugin] (JENKINS-26388) Jenkins think the image cap is reached although it's not and cannot spawn new slaves

[asaglio...@gmail.com (JIRA)]

Antonio Sagliocco created JENKINS-26388 Jenkins think the image cap is reached although it's not and cannot spawn new slaves Issue Type: Bug Assignee: Unassigned Components: docker-plugin Created: 12/Jan/15 10:26 AM Description: Jenkins reports that the cap is reached and it's not possible to spawn new slaves: Jan 12, 2015 9:41:54 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision Excess workload after pending Spot instances: 4 Jan 12, 2015 9:41:54 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud countCurrentDockerSlaves Images found: [Image{repository=null, tag=null, id=58f7c5283c6d4d5df99c3594c99943aec38324da3734e327c9f0337dd48451e3, created=1418900954, size=0, virtualSize=2063934469}] Jan 12, 2015 9:41:54 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave Total container cap of 5 reached, not provisioning. Reality is that there is only one slave running and the /docker-plugin view tracks the active hosts correctly. My guess: The DockerCloud#provisioningAmis hashtable is not updated consistently and goes out of sync Project: Jenkins Priority: Major Reporter: Antonio Sagliocco

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.