Comment 10 for bug 1470420
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (stable/mitaka) | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 8825efa3b263f13
Author: Rajesh Tailor <email address hidden>
Date: Thu Jul 2 03:22:01 2015 -0700
Set migration status to 'error' on live-migration failure
(A) In resize, confirm-resize and revert-resize operation, migration status
is marked as 'error' in case of failure for respective operation.
Migration object support is added in live-migration operation, which mark
migration status to 'failed' if live-migration operation fails in-between.
To make live-migration consistent with resize, confirm-resize and revert-
resize operation, it needs to mark migration status to 'error' instead of
'failed' in case of failure.
(B) Apart from consistency, proposed change fixes issue (similar to [1])
which might occur on live-migration failure as follows:
If live-migration fails (which sets migration status to 'failed') after
copying instance files from source to dest node and then user request for
instance deletion. In that case, delete api will only remove instance
files from instance.host and not from other host (which could be either
source or dest node but not instance.host). Since instance is already
deleted, instance files will remain on other host (not instance.host).
Set migration status to 'error' on live-migration failure, so that
periodic task _cleanup_
instance files from compute nodes after instance deletion in above case.
[1] https:/
[2] https:/
DocImpact: On live-migration failure, set migration status to 'error'
instead of 'failed'.
Change-Id: I7a0c5a32349b0d
Closes-Bug: 1470420
(cherry picked from commit d61e15818c1d108