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/491001 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=fe8acf003e8 e4d26f02ec38034 c4715dfb9888ba
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit fe8acf003e8e4d2 6f02ec38034c471 5dfb9888ba
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_
Conflicts:
nova/ tests/unit/ objects/ test_request_ spec.py
NOTE(mriedem): Conflict is due to d288132dca7cc76 dfc6679eda17bb8 fcc62577de
not being in Ocata, but it's not needed either.
Change-Id: Iba0b88172e9a3b fd4f216dd364d70 f7e01c60ee2 31f43db6ca9c21d b8aeb9007e) b0e39d6f1f3183f 616c2b90f7)
Closes-Bug: #1702454
(cherry picked from commit 69bef428bd555bb
(cherry picked from commit bceb176fb00104f