yahoo-eng-team team mailing list archive

[melanie witt <1784826@xxxxxxxxxxxxxxxxxx>]

I don't think this is a valid bug. The evacuate API use case is when the
compute host is dead, powered off, or otherwise completely disconnected
from the network such that the nova-compute service and instances cannot
be accessed. The force-down API is just a way for an operator to force a
compute host as "down" without having to wait for the service update
interval to reflect "down".

The operator must completely "fence" or "wall off" the compute host
before calling the evacuate API, if the compute host is not already dead
or powered off. If you evacuate instances without fencing the compute
host, you are in danger of corrupting data because duplicate instances
will be running potentially connected to the same disk at the same time
(if shared storage) and connected to same network port, same volume,
etc.

** Changed in: nova
       Status: In Progress => Invalid

-- 
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):
  Invalid

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