Fixed clean up process in confirm_resize() after resize/cold migration
On env with NUMA topology and enabled cpu pinning we have one problem.
If instance changes numa node (or even pinned cpus in numa node)
during cold migration from one host to another confirming resize
failed with "Cannot pin/unpin cpus from the following pinned set".
It happening because confirm_resize() tries to clean up source
host using numa topology from destination host.
Closes-Bug: #1564393
Change-Id: I3b87be3f25fc0bce4efd9804fa562a6f66355464
(cherry picked from commit d7b8d997f0a7d40055c544470533e8a11855ff8f)
Reviewed: https:/ /review. fuel-infra. org/21619
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka
Commit: 780464b9e83a303 4cd9dac940d4236 96aa063500
Author: Sergey Nikitin <email address hidden>
Date: Fri Jun 3 09:49:13 2016
Fixed clean up process in confirm_resize() after resize/cold migration
On env with NUMA topology and enabled cpu pinning we have one problem.
If instance changes numa node (or even pinned cpus in numa node)
during cold migration from one host to another confirming resize
failed with "Cannot pin/unpin cpus from the following pinned set".
It happening because confirm_resize() tries to clean up source
host using numa topology from destination host.
Closes-Bug: #1564393
Change-Id: I3b87be3f25fc0b ce4efd9804fa562 a6f66355464 055c544470533e8 a11855ff8f)
(cherry picked from commit d7b8d997f0a7d40