yahoo-eng-team team mailing list archive

[Corey Bryant <corey.bryant@xxxxxxxxxxxxx>]

Liang, thanks for the patches. LGTM. I'll upload once a local build
passes.

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** No longer affects: cloud-archive

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/icehouse
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => Invalid

** Changed in: cloud-archive
       Status: Invalid => Fix Released

** Changed in: cloud-archive/icehouse
       Status: New => In Progress

** Changed in: cloud-archive/icehouse
   Importance: Undecided => Medium

** Changed in: cloud-archive
   Importance: Undecided => Medium

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

Title:
  nova should allow evacuate for an instance in the Error state

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive icehouse series:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * Instances in error state cannot be evacuated.

  [Test Case]

   * nova evacuate <error_state_instance> <another_compute_host>
   * nova refuses to evacuate the instance because of its state

  [Regression Potential]

   * None
   * Passed tempest smoke tests locally.

  Note: one simple way to put an instance into error state is to
  directly change its database record, for example "update instances set
  vm_state='error' where uuid='XXXXXXXX'"


  We currently allow reboot/rebuild/rescue for an instance in the Error
  state if the instance has successfully booted at least once.

  We should allow "evacuate" as well, since it is essentially a
  "rebuild" on a different compute node.

  This would be useful in a number of cases, in particular if an initial
  evacuation attempt fails (putting the instance into the Error state).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1298061/+subscriptions