-
Committer:
MaaS Lander
-
Author(s):
jtv at canonical
-
Date:
2014-08-08 20:07:46 UTC
-
mfrom:
(2662.2.6 bug-1354511)
-
Revision ID:
maas_lander-20140808200746-i4b2zqjl4y4jy17e
[r=blake-rouse][bug=1354511][author=jtv] When timing out nodes that haven't finished commissioning, compare the last-update timestamp to the database clock (from which it was also generated), not to the Python-side clock. Timezone skew between the two could cause nodes to time out immediately, or hours late.