Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Live migration failure in API leaves VM in MIGRATING state
When nova-api calls nova-conductor a RPC MessagingTimeout might occur. In such case we shouldn't leave VM in MIGRATING state. Possible scenarios are: * nova-conductor received message but failed to respond, no additional exceptions raised - live migration will start, VM will be moved to destination host * nova-conductor received message but failed to respond, additional exception raised (e.g., LibvirtError) - LM will not start * nova-api couldn't reach nova-conductor - LM will not start Because we can't predict in API layer what happened below, this patch writes instance fault to database when MessagingTimeout is caught. Co-Authored-By: Pawel Koniszewski <pawel.koniszewski@intel.com> Bartosz Fic <bartosz.fic@intel.com> Closes-Bug: #1276214 Change-Id: Id800e925fbb689d20e7907b698b67c92fd3da979 (cherry picked from commit f2a1f00)
- Loading branch information
Showing
2 changed files
with
36 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters