yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74186
[Bug 1785031] Re: live migration to non-existing host gets instance stuck in "migrating" status
This is really a duplicate bug and the original fix is here:
https://review.openstack.org/#/c/401009/
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova/ocata
Importance: Undecided => Medium
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova
Assignee: Chen (chenn2) => 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/1785031
Title:
live migration to non-existing host gets instance stuck in "migrating"
status
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) ocata series:
Confirmed
Status in OpenStack Compute (nova) pike series:
Confirmed
Status in OpenStack Compute (nova) queens series:
Confirmed
Bug description:
Description
===========
When doing live-migration, if a host that does not exist or cannot be found is specified as destination, live-migration will fail and instance will get stuck in status "migrating".
Steps to reproduce
==================
nova live-migration vm non_existing_host
Expected result
===============
live-migration fails and instance rolls back to initial state
Actual result
=============
live-migration fails but instance's status remains "migrating"
Environment
===========
nova --version
10.1.0 (queens release)
Logs & Configs
==============
not related
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1785031/+subscriptions
References