yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01538
[Bug 1131588] Re: virt drivers' resume_state_on_host_boot don't handle migrating instances
** Changed in: nova
Status: Fix Committed => 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/1131588
Title:
virt drivers' resume_state_on_host_boot don't handle migrating
instances
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
nova-compute's init_host() can attempt to resume instances that are
found not to be in RUNNING power state... but should be.
For xenapi, the driver just tries to 'power on' the instance.
For libvirt, it tries to do a hard reboot.
Neither method account for 'resize_migrating' task state... where (at
least in XenAPI), the instance would have been renamed to append
'-orig' to it. The driver will raise NotFound because it can't find
the instance.
nova-compute's init_host() will catch all Exceptions and set the
instance to ERROR... but it seems that since we have code to clean up
the destination (there's code that looks at all instances in the
driver and looks to see if their 'host' changed... and destroys them
if so)... we could potentially clean up the source as well. Rename
the instance back, clear task_state, and restart the old instance?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1131588/+subscriptions