Incorrect cellid in NUMA memnode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Rafael Folco |
Bug Description
Description
===========
Nova generating wrong cellid for numa memnode.
Some systems number nodeset for the NUMA topology in non-sequential way, as follows:
node 0 1 16 17
Steps to reproduce
==================
Create a flavor w/ hw:numa_nodes=4 (hw:cpu_policy unset)
Spawn an instance across multiple nodes
Check nodeset in the instance XML
Expected result
===============
Correct cellid:
<memnode cellid='0' mode='strict' nodeset='0'/>
<memnode cellid='1' mode='strict' nodeset='1'/>
<memnode cellid='2' mode='strict' nodeset='16'/>
<memnode cellid='3' mode='strict' nodeset='17'/>
Actual result
=============
Wrong cellid:
<memnode cellid='0' mode='strict' nodeset='0'/>
<memnode cellid='1' mode='strict' nodeset='1'/>
<memnode cellid='16' mode='strict' nodeset='16'/>
<memnode cellid='17' mode='strict' nodeset='17'/>
Environment
===========
Ubuntu Xenial 16.10, OpenStack Mitaka release, Libvirt 1.3.1
Note: This issue has been found / tested on Ubuntu KVM on Power (ppc64le arch), however, it *may* affect other architectures.
tags: | added: numa |
Fix proposed to branch: master /review. openstack. org/340599
Review: https:/