Public bug reported: 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 ** Affects: nova Importance: Medium Status: Triaged ** Tags: evacuate openstack-version.pike placement -- 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): Triaged 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
