From a7c0a84a1e50a9f83acd27ece64f393ac454cf7f Mon Sep 17 00:00:00 2001 From: Anusha Unnam Date: Mon, 29 Aug 2016 21:09:48 +0000 Subject: [PATCH] Add a new release note Add a new reno note to specify that migration status is changed from 'failed' to 'error' on live-migration failure. That was landed as change I7a0c5a32349b0d3604802d22e83a3c2dab4b1370 Change-Id: I4e1693fa52bcb33b8770ec59640890abd2b911c8 Closes-bug: #1588888 --- ...error_on_live-migration_failure-d1f6f29ceafdd598.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/set_migration_status_to_error_on_live-migration_failure-d1f6f29ceafdd598.yaml diff --git a/releasenotes/notes/set_migration_status_to_error_on_live-migration_failure-d1f6f29ceafdd598.yaml b/releasenotes/notes/set_migration_status_to_error_on_live-migration_failure-d1f6f29ceafdd598.yaml new file mode 100644 index 000000000000..f2a0c216dc3e --- /dev/null +++ b/releasenotes/notes/set_migration_status_to_error_on_live-migration_failure-d1f6f29ceafdd598.yaml @@ -0,0 +1,9 @@ +--- +fixes: + - To make live-migration consistent with resize, confirm-resize and + revert-resize operations, the migration status is changed to 'error' + instead of 'failed' in case of live-migration failure. With this change + the periodic task '_cleanup_incomplete_migrations' is now able to remove + orphaned instance files from compute nodes in case of live-migration + failures. There is no impact since migration status 'error' and + 'failed' refer to the same failed state.