Bug 1265953

Summary:	It is possible to set a non numa host as preferred host
Product:	[oVirt] ovirt-engine	Reporter:	Roman Mohr <rmohr>
Component:	Frontend.WebAdmin	Assignee:	Roman Mohr <rmohr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, dfediuck, mavital, mgoldboi, rgolan, rmohr, sbonazzo
Target Milestone:	ovirt-3.6.3	Keywords:	Triaged
Target Release:	3.6.3.3	Flags:	rule-engine: ovirt-3.6.z+ mgoldboi: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-11 07:25:29 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:
Bug Depends On:
Bug Blocks:	1279178, 1289967

Description Roman Mohr 2015-09-24 08:25:22 UTC

Description of problem:

When there is at least one numa host in a cluster it is not checked if the specific host which is selected from the "preferred host list" supports numa.

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


How reproducible:

In a cluster with hosts with numa and without numa, configure numa topology of a VM on a host 

Steps to Reproduce:
1. Add a host with numa support
2. Add a host without numa support
3. Create a new VM
4. Go to host tab, select "no migration allowed" and run on spiecific host
5. Select the host without numa support
6. Set the number of numa nodes
7. Save the configuration

Actual results:
It is possible to set the number of numa nodes and save that configuration.

Expected results:
The numa section should be greyed out, or at least saving that configuration should fail.

Additional info:

Comment 3 Roy Golan 2016-02-10 10:57:14 UTC

can you make sure it works on 3.6 as well as you already fixed that in another bug (please add the bug details and close dup if so)

Comment 4 Artyom 2016-02-26 12:51:33 UTC

Verified on rhevm-webadmin-portal-3.6.3.3-0.1.el6.noarch

1) add three hosts two with NUMA support and one without
2) change vm migration policy to "Not allow migration"
3) check numa parameters when check different specific host
NUMA parameters close for non-NUMA host and opened for NUMA host