Description of problem: Possible to add numa node with pinning to not pinned vm via REST Version-Release number of selected component (if applicable): rhevm-3.5.1-0.3.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Update vm(1024 memory, 2 CPU's) via UI under Host tab to: Start Running On: some specific host with numa Leave migration options: Allow manual or automatic migration 2. Try to add numa pinned node via REST <vm_numa_node> <index>0</index> <memory>1024</memory> <cpu> <cores> <core index="0"/> <core index="1"/> </cores> </cpu> <numa_node_pins> <numa_node_pin pinned="true" index="index_of_host_numa_node"> <host_numa_node href= "/ovirt-engine/api/hosts/host_id/numanodes/numa_node_id" id="numa_node_id"> </host_numa_node> </numa_node_pin> </numa_node_pins> </vm_numa_node> 3. Actual results: Action Success Expected results: Action failed, engine must show error message(failed to add pinned numa node, when vm not pinned to host) Additional info: Via UI I can not set numa nodes until I pin vm to host(Start Running On: some specific host with numa; Migration options: Do not allow migration) Bug is also actual for cases when Migration options: Allow manual migration only
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
The bug is already fixed in 3.6, but can only be seen after Bug 1248049 is fixed.
Verified on rhevm-restapi-3.6.0.3-0.1.el6.noarch Failed to add numa node to vm <fault> <reason>Operation Failed</reason> <detail>[Cannot ${action} ${type}. VM must be pinned to a host.]</detail> </fault>