Bug 1126180
Summary: | Remove or validate index for numaNodes under vm | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> |
Component: | RestAPI | Assignee: | Roman Mohr <rmohr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | --- | CC: | bugs, dfediuck, ecohen, gklein, iheim, mavital, rbalakri, rgolan, rmohr, yeylon, ylavi |
Target Milestone: | ovirt-3.6.3 | Keywords: | Reopened, Triaged |
Target Release: | --- | Flags: | rule-engine:
ovirt-3.6.z+
rule-engine: exception+ rule-engine: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+ |
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
The engine allowed the creation of numa nodes with arbitrary indices.
Consequence:
libvirt requires a continuous numa node index sequence for virtual numa nodes. As a result starting the VM failed in a non interactive way.
Fix:
Validate indices on all numa related operations (add, remove, modify nodes)
Result:
The user gets immediate feedback through UI or REST if the numa related command execution destroys the index sequence.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-11 07:24:04 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
Artyom
2014-08-03 08:16:51 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority (In reply to Artyom from comment #0) > Description of problem: > numaNode index is mandatory when create vm via REST and it also possible to > change index via update, but this index not affect on something and just add > complexity and bugs, for example if I create two numaNodes with the same > index, via REST I can see that two numa nodes appear, but vi numactl --show > on guest OS I can see just one NUMA node I see two bugs here: 1) The REST response looks like the change is immediately applied, but such changes only take effect after a restart. This will be fixed in Bug 1254910 2) The numNode index is currently mandatory but should not be there at all > Actual results: > Nodes created and I can see two NUMA nodes via REST, but on guest OS I can > see just one NUMA node Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag. This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag. Verified on rhevm-backend-3.6.3.2-0.1.el6.noarch <fault> <reason>Operation Failed</reason> <detail>[Expected a continuous sequence of 0-1 for 2 numa nodes. Missing indices 1. Assign indices with increasing order starting from 0 to your virtual numa nodes.]</detail> </fault> <fault> <reason>Operation Failed</reason> <detail>[NUMA node with index 0 exists at least twice.]</detail> </fault> |