yahoo-eng-team team mailing list archive

[huanhongda <1784826@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
If evacuate an instance from a nova-compute forced down host, after unset force-down the instance's guest will remain in origin host.
That's because while unset force-down nova-compute service, nova-compute will not destroy evacuated instances. 
And it will do destroy while restart nova-compute service.

Steps to reproduce
==================
1) Boot an instance on node-1.
2) Force down the nova-compute service on node-1.
   nova service-force-down node-1 nova-compute
3) Evacuate the instance to other host.
4) Unset force-down for node-1 nova-compute.
   nova service-force-down --unset node-1 nova-compute
5) Check the guest on node-1.
   virsh list

Expected result
===============
The guest should be deleted on node-1.

Actual result
=============
The guest still remain on node-1.

Environment
===========
This bug was found in Newton. I think it also exist in master as the code of unset force-down service is the same as Newton.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: evacuate

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

Title:
  Guest remain in origin host after evacuate and unset force-down nova-
  compute

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  If evacuate an instance from a nova-compute forced down host, after unset force-down the instance's guest will remain in origin host.
  That's because while unset force-down nova-compute service, nova-compute will not destroy evacuated instances. 
  And it will do destroy while restart nova-compute service.

  Steps to reproduce
  ==================
  1) Boot an instance on node-1.
  2) Force down the nova-compute service on node-1.
     nova service-force-down node-1 nova-compute
  3) Evacuate the instance to other host.
  4) Unset force-down for node-1 nova-compute.
     nova service-force-down --unset node-1 nova-compute
  5) Check the guest on node-1.
     virsh list

  Expected result
  ===============
  The guest should be deleted on node-1.

  Actual result
  =============
  The guest still remain on node-1.

  Environment
  ===========
  This bug was found in Newton. I think it also exist in master as the code of unset force-down service is the same as Newton.

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