yahoo-eng-team team mailing list archive

[OpenStack Infra <1643623@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/447355
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb68fd12e2fd6e9686ad45c9875508bd9fa0df91
Submitter: Zuul
Branch:    master

commit fb68fd12e2fd6e9686ad45c9875508bd9fa0df91
Author: Sivasathurappan Radhakrishnan <siva.radhakrishnan@xxxxxxxxx>
Date:   Mon Mar 20 03:13:13 2017 +0000

    Return 400 when compute host is not found
    
    Previously user was getting a 500 error code for ComputeHostNotFound
    if they are using latest microversion that does live migration in
    async. This patches changes return response to 400 as 500 internal
    server error should not be returned to the user for failures due to
    user error that can be fixed by changing to request on client side.
    
    Change-Id: I7a9de211ecfaa7f2816fbf8bcd73ebbdd990643c
    closes-bug:1643623


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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:
  Instance stuck in 'migrating' status due to invalid host

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  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

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