Bug 2078189

Summary:	Change an error returned when running together resize policy VM with the dedicated VM
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	BLL.Virt	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED NEXTRELEASE	QA Contact:	Polina <pagranat>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.5.0.4	CC:	ahadas, bugs, dfodor, mperina, mzamazal
Target Milestone:	ovirt-4.5.3	Flags:	mperina: ovirt-4.5+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-19 14:31:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Polina 2022-04-24 09:37:59 UTC

Description of problem:

resize policy VM is forbidden to run together with dedicated. event if there are CPU resources. that's why I'm not sure that the error text we get now is good. 

"the host host_mixed_1 did not satisfy internal filter CpuPinning because doesn't have enough CPUs for the resize and pin NUMA CPU policy that the VM is set with."

The error must be more explicit and should say about exclusively running rule

Version-Release number of selected component (if applicable):
ovirt-engine-4.5.0.2-0.7.el8ev.noarch

How reproducible:


Steps to Reproduce:
On host with topology 1:4:1 (sockets:cores:threads) run one dedicated 1:2:1 and one resize_and_pin_numa VM 


Actual results:error 
"the host host_mixed_1 did not satisfy internal filter CpuPinning because doesn't have enough CPUs for the resize and pin NUMA CPU policy that the VM is set with."

Expected results:
the error should say about exclusively running rule

Additional info:

Comment 1 Casper (RHV QE bot) 2022-09-19 14:31:20 UTC

This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.