| 2016-11-21 16:59:13 |
Sivasathurappan Radhakrishnan |
bug |
|
|
added bug |
| 2016-11-21 16:59:40 |
Sivasathurappan Radhakrishnan |
tags |
|
live-migration |
|
| 2016-11-21 16:59:58 |
Sivasathurappan Radhakrishnan |
nova: assignee |
|
Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
|
| 2016-11-22 01:46:47 |
Matt Riedemann |
nova: status |
New |
Incomplete |
|
| 2016-11-22 18:21:51 |
Sivasathurappan Radhakrishnan |
description |
Tried to live migrate instance to destination host which was an invalid one. Got a error message saying host was not available <class 'nova.exception.ComputeHostNotFound'>. Did a nova list and found status and task state was stuck in migrating status forever. Couldn't see the instance in 'nova migration-list' and not able to abort the migration using 'nova live-migration-abort'.
Steps to reproduce:
1) Create an instance test_1
2) live migrate instance using 'nova live-migration test_1 <invalid destination host name>'
3) Check status of the instance using 'nova show test_1' or 'nova list'.
Expected Result:
Status of the instance should have been in Active status as live migration failed with invalid host name
Actual Result:
Instance is stuck in 'migrating' status forever.
Environment:
Multinode devstack environment with 2 compute nodes
1)Current master
2)Networking-neutron
3)Hypervisor Libvirt-KVM |
Tried to live migrate instance to destination host which was an invalid one. Got a error message saying host was not available <class 'nova.exception.ComputeHostNotFound'>. Did a nova list and found status and task state was stuck in migrating status forever. Couldn't see the instance in 'nova migration-list' and not able to abort the migration using 'nova live-migration-abort'.
Steps to reproduce:
1) Create an instance test_1
2) live migrate instance using 'nova live-migration test_1 <invalid destination host name>'
3) Check status of the instance using 'nova show test_1' or 'nova list'.
Expected Result:
Status of the instance should have been in Active status as live migration failed with invalid host name
Actual Result:
Instance is stuck in 'migrating' status forever.
Environment:
Multinode devstack environment with 2 compute nodes or it can be done in single node environment as the validation of host name happens before live migration.
Multinode environment is not really required to reproduce above scenario
1)Current master
2)Networking-neutron
3)Hypervisor Libvirt-KVM |
|
| 2016-11-22 18:32:00 |
Sivasathurappan Radhakrishnan |
summary |
Not able to abort live migration |
Instance stuck in 'migrating' status due to invalid host |
|
| 2016-11-22 18:33:44 |
Sivasathurappan Radhakrishnan |
description |
Tried to live migrate instance to destination host which was an invalid one. Got a error message saying host was not available <class 'nova.exception.ComputeHostNotFound'>. Did a nova list and found status and task state was stuck in migrating status forever. Couldn't see the instance in 'nova migration-list' and not able to abort the migration using 'nova live-migration-abort'.
Steps to reproduce:
1) Create an instance test_1
2) live migrate instance using 'nova live-migration test_1 <invalid destination host name>'
3) Check status of the instance using 'nova show test_1' or 'nova list'.
Expected Result:
Status of the instance should have been in Active status as live migration failed with invalid host name
Actual Result:
Instance is stuck in 'migrating' status forever.
Environment:
Multinode devstack environment with 2 compute nodes or it can be done in single node environment as the validation of host name happens before live migration.
Multinode environment is not really required to reproduce above scenario
1)Current master
2)Networking-neutron
3)Hypervisor Libvirt-KVM |
Tried to live migrate instance to invalid destination host. Got an error message saying host was not available <class 'nova.exception.ComputeHostNotFound'>. Did a nova list and found status and task state was stuck in migrating status forever. Couldn't see the instance in 'nova migration-list' and not able to abort the migration using 'nova live-migration-abort' as the operation was aborted well before migration id could be set.
Steps to reproduce:
1) Create an instance test_1
2) live migrate instance using 'nova live-migration test_1 <invalid destination host name>'
3) Check status of the instance using 'nova show test_1' or 'nova list'.
Expected Result:
Status of the instance should have been in Active status as live migration failed with invalid host name
Actual Result:
Instance is stuck in 'migrating' status forever.
Environment:
Multinode devstack environment with 2 compute nodes or it can be done in single node environment as the validation of host name happens before live migration.
Multinode environment is not really required to reproduce above scenario
1)Current master
2)Networking-neutron
3)Hypervisor Libvirt-KVM |
|
| 2016-11-23 00:24:48 |
OpenStack Infra |
nova: status |
Incomplete |
In Progress |
|
| 2017-02-10 14:13:17 |
John Garbutt |
nova: importance |
Undecided |
Medium |
|
| 2018-01-30 16:39:46 |
Sivasathurappan Radhakrishnan |
nova: assignee |
Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
|
|
| 2018-02-01 12:13:43 |
Rajesh Tailor |
nova: assignee |
|
Rajesh Tailor (ratailor) |
|
| 2018-02-09 11:47:19 |
Lukas Stehlik |
bug |
|
|
added subscriber Lukas Stehlik |
| 2018-03-07 13:43:02 |
OpenStack Infra |
nova: status |
In Progress |
Fix Released |
|
| 2018-03-29 03:31:53 |
OpenStack Infra |
tags |
live-migration |
in-stable-queens live-migration |
|
| 2018-03-30 18:37:11 |
OpenStack Infra |
tags |
in-stable-queens live-migration |
in-stable-pike in-stable-queens live-migration |
|
| 2018-08-03 17:05:50 |
Matt Riedemann |
nova: assignee |
Rajesh Tailor (ratailor) |
Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
|
| 2018-09-19 16:30:37 |
OpenStack Infra |
tags |
in-stable-pike in-stable-queens live-migration |
in-stable-ocata in-stable-pike in-stable-queens live-migration |
|
