| 2016-01-21 11:36:41 |
Radomir Dopieralski |
description |
If during live migration the connection to nova conductor service is somehow lost (for instance, due to the rabbitmq server becoming unavailable), the migration status of the nodes never gets updated, and they end up forever in "migrating" state, with the actual guest already running on the new host, but the data in the nova database still pointing at the old host.
This happens in all versions at lest up to Mitaka.
How to reproduce:
1. Create a simple setup with two hosts.
2. Create an instance and start a live migration.
3. Kill the rabbitmq server.
4. Wait for the migration to finish.
5. Bring the rabbitmq server back up.
6. Observe the instance stuck in "migrating" state, with everything migrated o the new host, but Nova thinking it's still on the old host. |
If during live migration the connection to nova conductor service is somehow lost (for instance, due to the rabbitmq server becoming unavailable), the migration status of the nodes never gets updated, and they end up forever in "migrating" state, with the actual guest already running on the new host, but the data in the nova database still pointing at the old host.
This happens in all versions at lest up to Mitaka.
How to reproduce:
1. Create a simple setup with two hosts.
2. Create an instance and start a live migration.
3. Kill the rabbitmq server.
4. Wait for the migration to finish.
5. Bring the rabbitmq server back up.
6. Observe the instance stuck in "migrating" state, with everything migrated to the new host, but Nova thinking it's still on the old host. |
|
