Looks like the compute service provides the exception, but you only give us the conductor one. Could you please provide the nova-compute.log that returns this exception so we can verify which decorated RPC method returns this ?
Also, please note we changed in v2.34 how live-migration pre-flight checks were done. See http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/async-live-migration-rest-check.html for the detailed reasoning behind that and https://review.openstack.org/#/c/314932/18/releasenotes/notes/async-live-migration-rest-check-675ec309a9ccc28e.yaml for the according release note.
For some reason, looks like the instance action record wasn't correctly persisted, so when trying to get it for adding the start event, it fails...
Looks like the compute service provides the exception, but you only give us the conductor one. Could you please provide the nova-compute.log that returns this exception so we can verify which decorated RPC method returns this ?
Also, please note we changed in v2.34 how live-migration pre-flight checks were done. See http:// specs.openstack .org/openstack/ nova-specs/ specs/newton/ implemented/ async-live- migration- rest-check. html for the detailed reasoning behind that and https:/ /review. openstack. org/#/c/ 314932/ 18/releasenotes /notes/ async-live- migration- rest-check- 675ec309a9ccc28 e.yaml for the according release note.
For some reason, looks like the instance action record wasn't correctly persisted, so when trying to get it for adding the start event, it fails...