Instances should not have soft-affinity with themselves.
Bug #1564559 reported by
Mark Doffman
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
When migrating instances should not have affinity with themselves.
This is most clearly seen with hard anti-affinity as an instance attempting to migrate to the same host would be unable to do so due to the presence of 'itself' on the host. (See bug #1558532).
In the soft-affinity case the consequences are not so dire, but can lead to incorrect weights being calculated. This is due to the fact that the soft affinity weigher counts the instance that is being migrated when looking at the number of instances from the group on a host.
See: https:/
Changed in nova: | |
importance: | Undecided → Low |
assignee: | nobody → Mark Doffman (mjdoffma) |
tags: | added: scheduler |
Changed in nova: | |
assignee: | nobody → Charlotte Han (hanrong) |
Changed in nova: | |
assignee: | Charlotte Han (hanrong) → nobody |
To post a comment you must log in.
related to https:/ /bugs.launchpad .net/nova/ +bug/1558532
I think this patch can modify this question.
https:/ /review. openstack. org/#/c/ 299045/ 1/nova/ scheduler/ utils.py make instance's host is not contained with members = set(request_ spec.instance_ group.members) .
But this patch Solution had been denied, because we don't this this _SoftAffinityWe igherBase.