Author: Sivasathurappan Radhakrishnan <siva.radhakrish...@intel.com>
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.
** 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).
Instance stuck in 'migrating' status due to invalid host
Status in OpenStack Compute (nova):
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'.
Status of the instance should have been in Active status as live migration
failed with invalid host name
Instance is stuck in 'migrating' status forever.
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
Multinode environment is not really required to reproduce above scenario
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : email@example.com
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp