nodepool/nodepool/tests
Tobias Henkel b6a3e319e7
Update node during lockNode
After locking a node we most of the time update a node to double check
if the state changed on us. This is important to not operate on stale
data as we only have a guarantee that the node data is updated if we
update the data after getting the lock (regardless if we operate on
cached data or not).. However it is cumbersome to do this after every
lockNode call so doing this centrally reduces the risk to forget that.

This does not introduce any behavior change.

Change-Id: I06001e487041a3b67d969070b43f491c4ed3dce0
2018-11-26 19:37:41 +01:00
..
fixtures Add tox functional testing for drivers 2018-11-01 15:33:44 +01:00
functional Add tox functional testing for drivers 2018-11-01 15:33:44 +01:00
unit Update node during lockNode 2018-11-26 19:37:41 +01:00
__init__.py Use pipelines for stats keys 2018-07-25 16:46:13 +10:00
fake-image-create Add --checksum support to disk-image-create 2016-12-07 10:25:06 -05:00