yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53710
[Bug 1602023] [NEW] Incorrect cellid in NUMA memnode
Public bug reported:
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.
** Affects: nova
Importance: Undecided
Assignee: Rafael Folco (rafaelfolco)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1602023
Title:
Incorrect cellid in NUMA memnode
Status in OpenStack Compute (nova):
In Progress
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1602023/+subscriptions
Follow ups