[Buildbot] #3051: master refuses to schedule new builds, doesn't really stop nor start

[Buildbot trac]

#3051: master refuses to schedule new builds, doesn't really stop nor start
-------------------+------------------------
Reporter:  Ben     |       Owner:
    Type:  defect  |      Status:  new
Priority:  major   |   Milestone:  undecided
 Version:  master  |  Resolution:
Keywords:          |
-------------------+------------------------

Comment (by Ben):

 No new build is being scheduled.

 I have requests pending in the queue for latent and non-latent slaves. The
 web interface shows build requests for some builders. When I start my
 master, nothing happens. The  slaves are attaching themselves, a docker
 container is being created, but still, no build is started. (the docker
 slave doesn't seems to be acknowledged as being attached ny the master).

 If I wait long enough, the docker container is killed (and removed) as
 expected.

 When I stop my master, all process goes away.

 If I were to throw a wild guess at this, I'd say that the multi-master
 non-synchronization is again playing bad with me ... But this is just a
 wild guess based on previous experience, no current observation is
 pointing at this in this case.

--
Ticket URL: <http://trac.buildbot.net/ticket/3051#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation