Ruby Loo 62c6377adf Node should reflect what was saved ... After a node is saved to the database, we weren't updating the Node object to reflect what was saved. This caused a problem where the node's update_at field was incorrect. It was fixed in 065326c0f5 by explicitly setting node.update_at. However, that doesn't address other node fields that may be out of sync. The more correct fix would be to do a similar thing that (most of) the other Objects do, which is for the node to update itself via ._from_db_object(). Doing this revealed several incorrect tests and code in the conductor and agent where changes to the node's dictionaries were incorrectly being set and thus, not being saved. Those are fixed in this patch. Change-Id: Ia84cd60c1a4eabcc1ad0a756124c338fa9f644c8 Closes-Bug: #1679297 Related-Bug: #1281638		2017-04-04 09:19:31 -04:00
..
notes	Node should reflect what was saved	2017-04-04 09:19:31 -04:00
source	Use specific end version since liberty is EOL	2017-02-16 17:36:32 +00:00