1.1.1 Docker containers are spawend too late

• [1.1.1] docker-plugin version you use
• [ 2.98.1] jenkins version you use
• [ 17.05.0-ce] docker engine version you use

When new slave/docker container is spawned I see: Dec 13, 2017 5:16:38 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFO: Asked to provision 1 slave(s) for: label_name Dec 13, 2017 5:16:38 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFO: Will provision 'image_name', for label: 'label_name', in cloud: 'cloud_name' Dec 13, 2017 5:16:38 PM com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave

And as results I see successfully provisioned slave. But sometimes I see some new jobs waiting in queue, which should be executed on labels releated with dockers, but new slaves are not provisioned. Jobs waiting in that shape even about 10minutes. I dont see in logs(at this time) any new entrys from com.nirima.jenkins.plugins.docker

Edit: I enabled some more logs and i see: Dec 13, 2017 6:08:16 PM FINEST io.jenkins.docker.FastNodeProvisionerStrategy applyFoCloud Available executors=0, connecting=0, planned=10 Dec 13, 2017 6:08:16 PM FINE io.jenkins.docker.FastNodeProvisionerStrategy applyFoCloud Available capacity=10, currentDemand=7 Dec 13, 2017 6:08:16 PM FINE io.jenkins.docker.FastNodeProvisionerStrategy applyFoCloud Provisioning completed

My question is why planned value is so high and what does it mean? Looks like capacity is sum of (executors, connecting and planned) and new slaves are spawned only when capacity< currentDemand

[sporkisfaster]

Still having this issue. Getting Jenkins doesn’t have label testslave in any job configuration in jenkins. Tried pipeline, freestyle, etc. Tried SSH injection, manually pasting the key, JNLP, etc. Made sure there were no leading spaces in the label name. Not sure what’s going on.

Jenkins: v 2.100 Docker plugin 1.1.2 Version = 17.07.0-ce, API Version = 1.31

[pjdarton]

@missedone FYI the provisioning failure mentioned there is also logged in the logs. …and the next release has better help text for this feature, plus the ability to configure how long Jenkins remembers these errors for.