Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1099814

Summary: Missing node index when creating vm numa node
Product: [Retired] oVirt Reporter: Bruce Shi <xiao-lei.shi>
Component: ovirt-engine-coreAssignee: Bruce Shi <xiao-lei.shi>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5CC: alukiano, bugs, gklein, iheim, rbalakri, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: ovirt-3.5.0_rc3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:39:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bruce Shi 2014-05-21 09:09:16 UTC 
Description of problem:
When user create vm numa nodes, engine didn't fill the vm numa node index in the xmlrpc. Thus when vdsm create vm numa nodes in libvirt, it may cause the node index and actually created vm numa node mismatch.(In libvirt xml, no index of vm numa node, the index is decided with the created sequence)

Version-Release number of selected component (if applicable):
3.5.0-alpha1

How reproducible:
50%

Steps to Reproduce:
1.Try to create several vm numa nodes to a vm.
2.
3.

Actual results:
Sometimes the vm numa node index in engine side is not matched with the created vm numa nodes in vdsm side.

Expected results:
They should be matched all the time.

Additional info:
Comment 1 Jiri Moskovcak 2014-08-06 07:27:13 UTC 
*** Bug 1126182 has been marked as a duplicate of this bug. ***
Comment 2 Artyom 2014-10-01 08:14:42 UTC 
Verified on vt4
Comment 3 Sandro Bonazzola 2014-10-17 12:39:01 UTC 
oVirt 3.5 has been released and should include the fix for this issue.