Jenkins think the image cap is reached although it's not and cannot spawn new slaves

This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      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

            Assignee:
            Kanstantsin Shautsou
            Reporter:
            Antonio Sagliocco
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: