Dan Smith 604819b29c Always read-deleted=yes on lazy-load ... For some reason we were only reading deleted instances when loading generic fields and not things like flavor. That weird behavior isn't very helpful, so this makes us always read deleted for that case. Some of the fields, like tags, will short-circuit that and just immediately lazy-load an empty set. But for anything else, we should allow reading that data if it's still there. With this change, we are able to remove a specific read_deleted='yes' usage from ComputeManager._destroy_evacuated_instances() which is handled with the generic solution. TestEvacuateDeleteServerRestartOriginalCompute asserts that the evacuate scenario is still fixed. Related-Bug: #1794996 Related-Bug: #1745977 Change-Id: I8ec3a3a697e55941ee447d0b52d29785717e4bf0		2018-11-27 12:42:48 -05:00
..
functional	Refactor TestEvacuateDeleteServerRestartOriginalCompute	2018-11-27 12:42:48 -05:00
live_migration/hooks	Add post-test hook for testing evacuate	2018-10-25 16:15:56 -04:00
unit	Always read-deleted=yes on lazy-load	2018-11-27 12:42:48 -05:00
__init__.py
fixtures.py	Make CellDatabases fixture reentrant	2018-10-24 13:58:10 -07:00
json_ref.py	Transform instance.exists notification	2018-06-05 12:51:30 +00:00