Instance stuck in 'migrating' status due to invalid host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Sivasathurappan Radhakrishnan |
Bug Description
Tried to live migrate instance to invalid destination host. Got an error message saying host was not available <class 'nova.exception
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-
3)Hypervisor Libvirt-KVM
tags: | added: live-migration |
Changed in nova: | |
assignee: | nobody → Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
description: | updated |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | nobody → Rajesh Tailor (ratailor) |
Changed in nova: | |
assignee: | Rajesh Tailor (ratailor) → Sivasathurappan Radhakrishnan (siva-radhakrishnan) |
What exact command did you use to run the abort command? And do you have a new enough python-novaclient to support that microversion?
That was added in microversion 2.24:
http:// docs.openstack. org/developer/ nova/api_ microversion_ history. html#id22
Looks like you need at least novaclient 3.3.0 for that:
https:/ /github. com/openstack/ python- novaclient/ commit/ 77e50cc91b328b1 f7681cfc6f31bc4 1e40ab214e
Also, do you see this error in the nova-compute logs when the abort fails?
https:/ /review. openstack. org/#/c/ 277971/ 19/nova/ virt/libvirt/ driver. py@5831