yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1105445] Re: Instance 'start' will fail after hypervisor reboot

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thang Pham <thang.g.pham@xxxxxxxxx>
Date: Thu, 20 Mar 2014 18:29:26 -0000
Reply-to: Bug 1105445 <1105445@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Confirmed => 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/1105445

Title:
  Instance 'start' will fail after hypervisor reboot

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Simple to reproduce this with libvirt.  Let's assume there' s a single
  VM running on the hypervisor in question.  Gracefully shutdown the
  instance in question via the guest OS and wait for the power stat to
  reflect that it is shutdown.  Then reboot the hypervisor, then attempt
  to call 'nova start <uuid>'.  This operation will fail, because the
  VIFs, block devices, etc are all missing.

  This comes down to us calling _create_domain() rather than
  _create_domain_and_network() within the libvirt driver.  The compute
  manager needs to pass more information into driver.power_on, so that
  we can rebuild the VIFs and block connections.  Basically, similar
  treatment to what we've already done for driver.resume(),
  driver.reboot(), etc.

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