yahoo-eng-team team mailing list archive

[wuhao <wuhao@xxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Some prose which explains more in detail what this bug report is
about. If the headline of this report is descriptive enough, skip
this section.

Steps to reproduce
===========
* Create a instance a compute node
* crash the compute node
* Evacuate instances on the node
* reboot the crashed node

Expected result
===============
The evacuated instance should be destroyed.

Actual result
=============
After crashed nova-compute restarts, the instance is still defined.

Environment
===========
I used stable Liberty. But I think it's still valid on the master.

** Affects: nova
     Importance: Undecided
     Assignee: wuhao (wuhao)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => wuhao (wuhao)

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

Title:
  Evacuated instances failed to destory on the source node

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Some prose which explains more in detail what this bug report is
  about. If the headline of this report is descriptive enough, skip
  this section.

  Steps to reproduce
  ===========
  * Create a instance a compute node
  * crash the compute node
  * Evacuate instances on the node
  * reboot the crashed node

  Expected result
  ===============
  The evacuated instance should be destroyed.

  Actual result
  =============
  After crashed nova-compute restarts, the instance is still defined.

  Environment
  ===========
  I used stable Liberty. But I think it's still valid on the master.

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