Numa topology not calculated for instance with numa_topology after upgrading to Mitaka
Bug #1636338 reported by
Erik Olof Gunnar Andersson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
This is related to this bug https:/
After upgrading to Mitaka with the above patch, a new bug surfaced. The bug is related to InstanceNUMACell having cpu_policy set to None. This causes cpu_pinning_
https:/
This will then trick computes with old NUMA instances into thinking that nothing is pinned, causing new instances with cpu_policy set to CPUAllocationPo
summary: |
Numa topology not calculated for instance with numa_topology after - upgrading from Kilo + upgrading to Mitaka |
Changed in nova: | |
assignee: | nobody → Prateek Arora (parora) |
Changed in nova: | |
importance: | Undecided → Medium |
tags: |
added: upgrade removed: upgrades |
To post a comment you must log in.
It looks like [1] changed the way cpu_pinning_ requested works without considering backwards compatibility for older instances (instances with InstanceNUMACell < 1.3 that don't store cpu_policy).
def cpu_pinning_ requested( self): CPUAllocationPo licy.DEDICATED
- return self.cpu_pinning is not None
+ return self.cpu_policy == obj_fields.
Maybe introducing some fallback to the old check if InstanceNUMACell < 1.3 will do the trick.
[1] https:/ /github. com/openstack/ nova/commit/ dfe6545329e6d7e 417615af44f6b55 88948699db