Bug 2074522

Summary:	Resize_and_pin policy can't be configured in one transaction if user sets vCPUS, Host pinning and policy.
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	Frontend.WebAdmin	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.5.0	CC:	ahadas, bugs, dfodor
Target Milestone:	ovirt-4.5.1	Flags:	pm-rhel: ovirt-4.5?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-23 05:54:58 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-12 12:01:47 UTC

Description of problem:
User is not allowed to open Edit window and set in one transaction the following: configure vCPUs (in system tab),  then pin to host in 'Host' tab and then resize policy in 'Resource Allocation' tab.

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

How reproducible: 100%


Steps to Reproduce:
1. Create VM on the base of the latest infra template.
2. Open Edit window and set the following:
   - 4 CPUs (Total Virtual CPUs system tab);
   - pin to specific host in 'Host' tab;
   - set resize policy in 'Resource Allocation' tab.
   - OK in the Edit window.

Actual results:
Error: Cannot edit VM. The VM NUMA configuration cannot be applied when using the CPU Pinning policy 'Resize and Pin NUMA'.
The user only could do this by configuring vCPUs + pint to host, then OK in Edit window. Then Reopen and set the policy

Expected results: Must be allowed by one transaction

Comment 1 Lucia Jelinkova 2022-04-22 12:42:05 UTC

Yes, I agree, that is not user friendly.

Comment 2 Lucia Jelinkova 2022-05-27 11:56:58 UTC

Please note that setting the vCPUs number (or modification of NUMA) is still not allowed, because it will be automatically set by the Resize and Pin NUMA Cpu Pinning Policy. However, a new UI warning will be displayed that allows to reset the changed values and continue with saving of the VM.

Comment 3 Polina 2022-06-19 14:40:54 UTC

verified on ovirt-engine-4.5.1.2-0.11.el8ev.noarch according to the described scenario. the configuration is allowed in one transaction

Comment 4 Sandro Bonazzola 2022-06-23 05:54:58 UTC

This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.