yahoo-eng-team team mailing list archive

[OpenStack Infra <1709902@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/493037
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9b9c2c52f323c536fb90bb29a40efbed1b129594
Submitter: Jenkins
Branch:    master

commit 9b9c2c52f323c536fb90bb29a40efbed1b129594
Author: Balazs Gibizer <balazs.gibizer@xxxxxxxxxxxx>
Date:   Fri Aug 11 11:40:35 2017 +0200

    delete allocation of evacuated instance
    
    After evacuation the instance has allocations on both the source and
    the destination computes. This is OK as the source compute is down.
    However after the source compute is brought up the allocation from
    the source host needs to be cleaned up.
    
    Closes-Bug: #1709902
    Change-Id: I0df401a7c91f012fdb25cb0e6b344ca51de8c309


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  source host allocation not cleaned up in placement after evacuation

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  1) boot a server
  2) kill the compute (optionally force-down it)
  3) evacuate the server
  4) start up the original compute
  5) check the allocations in placement

  We expect that the allocation on the original compute is removed when that compute start up (init_host) after the evacuation but it isn't.
  The compute host periodic resource healing also skips this case here https://review.openstack.org/#/c/491850/4/nova/compute/resource_tracker.py@1084

  Here is a patch to reproduce the problem in the functional test env: https://review.openstack.org/#/c/492548/ 
  Here is the debug log for that run: https://pastebin.com/hzb33Awu

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