Cannot pin/unpin cpus during migration

[Andrey Epifanov]

Detailed bug description:
 Some VM after migration moved to ERROR state due failed of confirm_resize ().
 VM actually in running state on dest compute.
Steps to reproduce:
 Migration should take more time than update_resources_interval (needs to be checked)
Reproducibility:
 100%
Workaround:
 Reset state for VM to ACTIVE
Impact:
 Customers VMs often failed after migration
Description of the environment:
- Operation system: Ubuntu 14.04
- Versions of MOS: 9.2

Additional information:
- Suspect that it is the actual issue for master nova as well

I found similar bugs[1][2] in Openstack but fix already exists in the env.

[1]: https://bugs.launchpad.net/nova/+bug/1585214
[2]: https://bugs.launchpad.net/nova/+bug/1545675

[Alexander Rubtsov (arubtsov)]

The corresponding commit:
https://review.fuel-infra.org/#/c/37963/

[Dmitry Sutyagin (dsutyagin)]

Please see latest updates in https://mirantis.jira.com/browse/PROD-15177

[Alexander Rubtsov (arubtsov)]

The customer has confirmed that migration works well after applying the patch.
Please merge the fix to Mitaka branch.

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/37963
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: 1e9f18dabcbb1cd143966c31bccd2e7586a5cac2
Author: Andrey Volkov <email address hidden>
Date: Thu Mar 22 12:47:40 2018

Skip numa usage update for update_available_resource task

Current thoughts that update_available_resource could be the source
of troubles for CPU pin/unpin. New CPU pinning for migrated instance
could be incompatible with the old compute node. This causes fail
in periodic tasks like update_available_resource as it's check
resources for the old compute node. Effectively this means
that instance numa topology is updated but instance host is not.

This patch skips numa usage update while instance in a migration
state, for other states it's same as it was.

PROD: https://mirantis.jira.com/browse/PROD-15177
Change-Id: I542be52636d6aabc4ef93ed338ca89958ccb4cf2
Closes-Bug: #1751873

[Vladimir Jigulin (vjigulin)]

Closing the bug because we have a confirmation (#3) that the path works