| 2015-03-27 05:29:30 |
Eli Qiao |
bug |
|
|
added bug |
| 2015-03-27 05:29:40 |
Eli Qiao |
nova: assignee |
|
Eli Qiao (taget-9) |
|
| 2015-03-27 14:33:13 |
Davanum Srinivas (DIMS) |
nova: importance |
Undecided |
Low |
|
| 2015-03-27 14:33:16 |
Davanum Srinivas (DIMS) |
nova: status |
New |
Confirmed |
|
| 2015-06-01 11:22:49 |
Pawel Koniszewski |
tags |
|
live-migrate |
|
| 2015-07-27 02:07:02 |
Eli Qiao |
nova: status |
Confirmed |
Opinion |
|
| 2015-08-12 00:41:41 |
Eli Qiao |
nova: status |
Opinion |
Incomplete |
|
| 2015-10-20 12:06:47 |
Pawel Koniszewski |
nova: status |
Incomplete |
Confirmed |
|
| 2015-10-20 12:15:54 |
Pawel Koniszewski |
description |
I do a live-migration from host1 to host2
live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it)
nova list show that the instance is still active(actually , it is done the migration and I can see it host2 by virsh list)
taget@liyong:~/devstack$ nova list
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 |
show this instance, the instance's host is still host1(due to host1's compute crashed an no chance to set it yet).
after that. do a reboot on this instance, failed due to the instance can not be found from host1 host(yes, it is)
and nova set it to error status(but the instance is still running on host2) |
I do a live-migration from host1 to host2. If during live migration nova-compute service stops operating it will leave things in messy state. Even when live migration ends successfully from hypervisor perspective, nova does not update VM's host to new one. It also leaves VIFs and volume connections on source host.
nova list show that the instance is still active (actually it is because live migration has completed. However, nova loses track of a VM)
taget@liyong:~/devstack$ nova list
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 |
'nova show test1' shows that this instance is still on host1 (because service nova-compute on hsot1 crashed and it had no chance to update it).
After that any nova operation on this instance fails because nova tries to execute every operation on old host (after such fail nova changes instance state to error). |
|
| 2015-10-20 12:16:02 |
Pawel Koniszewski |
description |
I do a live-migration from host1 to host2. If during live migration nova-compute service stops operating it will leave things in messy state. Even when live migration ends successfully from hypervisor perspective, nova does not update VM's host to new one. It also leaves VIFs and volume connections on source host.
nova list show that the instance is still active (actually it is because live migration has completed. However, nova loses track of a VM)
taget@liyong:~/devstack$ nova list
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 |
'nova show test1' shows that this instance is still on host1 (because service nova-compute on hsot1 crashed and it had no chance to update it).
After that any nova operation on this instance fails because nova tries to execute every operation on old host (after such fail nova changes instance state to error). |
I do a live-migration from host1 to host2. If during live migration nova-compute service stops operating it will leave things in messy state. Even when live migration ends successfully from hypervisor perspective, nova does not update VM's host to new one. It also leaves VIFs and volume connections on source host.
nova list show that the instance is still active (actually it is because live migration has completed. However, nova loses track of a VM)
taget@liyong:~/devstack$ nova list
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | - | NOSTATE | private_net=10.0.0.9 |
'nova show test1' shows that this instance is still on host1 (because service nova-compute on host1 crashed and it had no chance to update it).
After that any nova operation on this instance fails because nova tries to execute every operation on old host (after such fail nova changes instance state to error). |
|
| 2015-10-20 12:16:48 |
Pawel Koniszewski |
summary |
instance 's host was not updated after live-migration if source compute host crash |
instance's host isnnot updated if nova-compute stops operating during live-migration |
|
| 2015-10-20 12:17:06 |
Pawel Koniszewski |
summary |
instance's host isnnot updated if nova-compute stops operating during live-migration |
instance's host isn't updated if nova-compute stops operating during live-migration |
|
| 2015-11-06 17:14:38 |
Paul Murray |
tags |
live-migrate |
live-migration |
|
| 2016-02-12 13:01:20 |
Pawel Koniszewski |
nova: assignee |
Eli Qiao (taget-9) |
|
|
