commit 604819b29c0bd43969747d32f6e3d818b3cbece7
Author: Dan Smith <email address hidden>
Date: Wed Jun 13 11:14:37 2018 -0700
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.
Reviewed: https:/ /review. openstack. org/575190 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=604819b29c0 bd43969747d32f6 e3d818b3cbece7
Committed: https:/
Submitter: Zuul
Branch: master
commit 604819b29c0bd43 969747d32f6e3d8 18b3cbece7
Author: Dan Smith <email address hidden>
Date: Wed Jun 13 11:14:37 2018 -0700
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 _destroy_ evacuated_ instances( ) which is handled with eteServerRestar tOriginalComput e asserts
from ComputeManager.
the generic solution. TestEvacuateDel
that the evacuate scenario is still fixed.
Related-Bug: #1794996
Related-Bug: #1745977
Change-Id: I8ec3a3a697e559 41ee447d0b52d29 785717e4bf0