Strange slave provisioning behavior

[jcsirot]

Hi!

On my Jenkins instance I am using the docker plugin in order to spawn slaves on demand. In the docker cloud configuration, each image is bound to a label and every job is also configured with a label indicating the docker image it requires. On this instance I set the master executor count to 0 and therefore I do not have any "permanent" executor. Moreover I do not have any unlabeled slave.

And now I have this unexpected behavior: when I start a job, two docker containers are started. According to the log hereunder, the first container is provisioned for the label "null" and the second container is provisioned for the label "wheezy64" (which is what I want since the job is actually configured with that label).

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision

Asked to provision 1 slave(s) for: null

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision

Will provision "jenkins:wheezy" for: null

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave

Provisioning "jenkins:wheezy" number 0 on "docker.adm.qa.arkena.com"; Total containers: 0

Mar 13, 2015 10:07:04 AM FINE com.nirima.jenkins.plugins.docker.DockerTemplate

Launching jenkins:wheezy

Mar 13, 2015 10:07:04 AM FINE com.nirima.jenkins.plugins.docker.DockerTemplateBase

Provisioning new container for image jenkins:wheezy

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision

Asked to provision 1 slave(s) for: wheezy64

Mar 13, 2015 10:07:04 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud provision

Will provision "jenkins:wheezy" for: wheezy64

Mar 13, 2015 10:07:05 AM INFO com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave

Provisioning "jenkins:wheezy" number 1 on "docker.adm.qa.arkena.com"; Total containers: 1

Mar 13, 2015 10:07:05 AM FINE com.nirima.jenkins.plugins.docker.DockerTemplate

Launching jenkins:wheezy

When i configure an unlabeled executor on the master the first provisioning request is never launched.

Is this a bug (and in that case I will open a Jira ticket) or did I miss something?

Thanks in advance.

[Marcus Sanchez]

I'm having the same issue, I had this working a day ago, but since I need to resinstall jenkinsthis stopo working.

Did you resolve this issue back in march?