yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1170328] Re: failed rescue should not error an instance

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

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

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

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

Title:
  failed rescue should not error an instance

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Currently if one attempts to put a VM into rescue mode and the
  operation fails. The VM is set to vm_state.ERROR.

  As a customer/end user, if I attempt to put my VM in rescue mode and
  it fails, I would like it to stay in ACTIVE mode so that I can pursue
  other repair options, such as reboot or migrate.

  If it's in ERROR status, only someone with admin api access can get it
  out again. For me (the end user) that means more down time while I
  find an admin to help me.

  ----

  If a rescue attempt fails, the VM's state should return to what it was
  before the rescue attempt started, and the user should be notified of
  the failure.

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