[Buildbot-commits] [Buildbot] #1780: Latent build slaves shut down uncleanly and get forgotten by the master

[Buildbot]

#1780: Latent build slaves shut down uncleanly and get forgotten by the master
---------------------------+--------------------
Reporter:  jacobian        |       Owner:
    Type:  defect          |      Status:  new
Priority:  major           |   Milestone:  0.8.4
 Version:  0.8.3p1         |  Resolution:
Keywords:  virtualization  |
---------------------------+--------------------

Comment (by jacobian):

 It helps a bit, and I've sorta been able to work around the failures (see
 https://github.com/jacobian/django-
 buildmaster/blob/master/djangobotcfg/rsc_slave.py).

 However, there's a more general problem which is that if stop_instance()
 fails (i.e. raises an exception) for any reason, then the master will
 remove that slave from the pool and never try to build a new one until
 after a server restart.

 As far as I can tell this sorta goes against the whole idea of a latent
 slave. I'd expect a latent slave failure to just affect that one build on
 that slave, and I'd expect Buildbot to boot me a new one.

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