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.
Change-Id: Iba0b88172e9a3bfd4f216dd364d70f7e01c60ee2
Closes-Bug: #1702454
(cherry picked from commit 69bef428bd555bb31f43db6ca9c21db8aeb9007e)
Reviewed: https:/ /review. openstack. org/516112 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=0c0023d0759 f54f5bd99d9ed29 c2a2ccb3965cba
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 0c0023d0759f54f 5bd99d9ed29c2a2 ccb3965cba
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 31f43db6ca9c21d b8aeb9007e)
Closes-Bug: #1702454
(cherry picked from commit 69bef428bd555bb