yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1188343] Re: Reboot should not change state to active until after the reboot completes

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 17 Jul 2013 12:21:57 -0000
Reply-to: Bug 1188343 <1188343@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

-- 
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/1188343

Title:
  Reboot should not change state to active until after the reboot
  completes

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  reboot_instance() in the compute manager currently changes the
  vm_state to active before it does anything else.

  If an instance was stopped (for example) and the reboot fails the
  vm_state is left as active

  It should leave the vm_state alone until the reboot has successfully
  completed, and then change to Active if it is not Rescued.

  It should also set vm_state to error if the reboot fails.
   
  See also this bug as to why going to Error is acceptable:
  https://bugs.launchpad.net/nova/+bug/1183946

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