When we added the requested_destination field for the RequestSpec object
in Newton, we forgot to pass it to the legacy dictionary when wanting to
use scheduler methods not yet supporting the NovaObject.
As a consequence, when we were transforming the RequestSpec object into a
tuple of (request_spec, filter_props) dicts and then rehydrating a new
RequestSpec object using those dicts, the newly created object was not
keeping that requested_destination field from the original.
Reviewed: https:/ /review. openstack. org/481116 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=7317afd3201 c4f9f21d3f37dab 08423dae236b17
Committed: https:/
Submitter: Zuul
Branch: master
commit 7317afd3201c4f9 f21d3f37dab0842 3dae236b17
Author: Sylvain Bauza <email address hidden>
Date: Thu Jul 6 17:17:31 2017 +0200
Pass requested_ destination in filter_properties
When we added the requested_ destination field for the RequestSpec object destination field from the original.
in Newton, we forgot to pass it to the legacy dictionary when wanting to
use scheduler methods not yet supporting the NovaObject.
As a consequence, when we were transforming the RequestSpec object into a
tuple of (request_spec, filter_props) dicts and then rehydrating a new
RequestSpec object using those dicts, the newly created object was not
keeping that requested_
Change-Id: Iba0b88172e9a3b fd4f216dd364d70 f7e01c60ee2
Closes-Bug: #1702454