#1954: Master fails to terminate EC2LatentBuildSlave
---------------------+-----------------------
Reporter: exarkun | Owner:
Type: defect | Status: new
Priority: critical | Milestone: undecided
Version: 0.8.3p1 | Keywords:
---------------------+-----------------------
On the first (and so far, only) substantiation of an EC2LatentBuildSlave,
the master failed to actually stop the instance. The logs have:
{{{
2011-05-10 17:36:23-0400 [-] disconnecting old slave bot-exarkun-2 now
2011-05-10 17:36:23-0400 [-] waiting for slave to finish disconnecting
2011-05-10 17:36:23-0400 [KeepaliveBroker,19,50.17.81.112]
BuildSlave.detached(bot-exarkun-2)
2011-05-10 17:36:26-0400 [KeepaliveBroker,20,50.17.81.112] Slave bot-
exarkun-2 received connection while not trying to substantiate.
Disconnecting.
2011-05-10 17:36:26-0400 [KeepaliveBroker,20,50.17.81.112] waiting for
slave to finish disconnecting
2011-05-10 17:36:26-0400 [KeepaliveBroker,20,50.17.81.112] Peer will
receive following PB traceback:
2011-05-10 17:36:26-0400 [KeepaliveBroker,20,50.17.81.112] Unhandled Error
Traceback (most recent call last):
Failure: exceptions.RuntimeError: Slave bot-exarkun-2 received
connection while not trying to substantiate. Disconnecting.
}}}
and apparently nothing else related to the issue. The result seems to be
that the instance will run forever, or until I intervene to correct the
situation.
--
Ticket URL: <http://trac.buildbot.net/ticket/1954>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
