Bug 2078189 - Change an error returned when running together resize policy VM with the dedicated VM
Summary: Change an error returned when running together resize policy VM with the dedi...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.5.0.4
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.5.3
: ---
Assignee: Shmuel Melamud
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-24 09:37 UTC by Polina
Modified: 2022-09-19 14:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-19 14:31:20 UTC
oVirt Team: Virt
Embargoed:
mperina: ovirt-4.5+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 620 0 None open webadmin: Change error for using resize policy with dedicated CPUs 2022-08-29 00:45:20 UTC
Red Hat Issue Tracker RHV-45856 0 None None None 2022-04-24 09:40:38 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.