yahoo-eng-team team mailing list archive

[Sivasathurappan Radhakrishnan <siva.radhakrishnan@xxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
     Assignee: Sivasathurappan Radhakrishnan (siva-radhakrishnan)
         Status: New


** Tags: live-migration

** Tags added: live-migration

** Changed in: nova
     Assignee: (unassigned) => Sivasathurappan Radhakrishnan (siva-radhakrishnan)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1643623

Title:
  Not able to abort live migration

Status in OpenStack Compute (nova):
  New

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1643623/+subscriptions