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.
Reviewed: https:/ /review. fuel-infra. org/37963
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka
Commit: 1e9f18dabcbb1cd 143966c31bccd2e 7586a5cac2
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 available_ resource as it's check
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_
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 bc4ef93ed338ca8 9958ccb4cf2
Change-Id: I542be52636d6aa
Closes-Bug: #1751873