Wenzhi Yu 1a80c8899d Report actual request_spec when MaxRetriesExceeded raised ... If a MaxRetriesExceeded exception is raised by scheduler_utils.populate_retry then request_spec will be empty in the exception handler[1], then _set_vm_state_and_notify method will just put a empty dict as request_spec into the payload of notification[2]. It would make more sense if we report the actual value of request_spec in the notification. [1]https://github.com/openstack/nova/blob/13.0.0.0rc3/nova/conductor/manager.py#L382 [2]https://github.com/openstack/nova/blob/13.0.0.0rc3/nova/scheduler/utils.py#L109 Simply moving the initialization of request_spec up one line before the call to populate_retry should fix the issue. Change-Id: I7c51f635d52f368c8df549f62024cbdf64a032b3 Closes-Bug: #1575998		2016-09-30 09:59:19 +08:00
..
tasks	Merge "Update RequestSpec nested flavor when a resize comes in"	2016-07-29 19:34:56 +00:00
__init__.py	Config options: centralize options in conductor api	2016-02-09 14:06:51 +00:00
api.py	Add async param to local conductor live_migrate_instance	2016-07-19 14:26:53 -04:00
manager.py	Report actual request_spec when MaxRetriesExceeded raised	2016-09-30 09:59:19 +08:00
rpcapi.py	Make live migration checks async	2016-06-23 02:50:45 +03:00