Bug 2099225

Summary: Numa number configuration setting is unexpectedly reverted.
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: Frontend.WebAdminAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5.1CC: ahadas, bugs, dfodor, mzamazal
Target Milestone: ovirt-4.5.2Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-30 08:47:42 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:
Attachments:
Description Flags
engine log none

Description Polina 2022-06-20 11:08:54 UTC 
Description of problem: we have two problematic flows here  - for running (Step2 )and not running VM (Step1).


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

How reproducible: 100 %


Steps to Reproduce:
1.Configure a not running VM with CPU=2 numa number = 2 and no host pinning. Edit VM - remove the numa number (put 0), then pin a host. = > 

Actual result: pinning the host automatically returns the numa number.
Expected: if I removed numa num , I don't expect that host pinning will revert this change. this is wrong.

2.For Running VM it is more critical : Run a VM configured with 4 CPUS , no host pinning and numa number = 2. Edit the running VM: replace numa number by 0, pin a host, note that the numa number is returned to 2, put 0 again. OK in the edit window. GET "Changes that require Virtual Machine restart:" message , OK.  Shutdown VM , start => it still has numa number 2.


Actual results: Restarted VM has initial numa number configuration 
Expected results: VM must have numa number 0.


Additional info:
Comment 1 Polina 2022-06-20 11:31:16 UTC 
Created attachment 1891282 [details]
engine log
Comment 2 Polina 2022-07-20 13:32:50 UTC 
verified according to description on ovirt-engine-4.5.1.3-0.36.el8ev.noarch
Comment 3 Sandro Bonazzola 2022-08-30 08:47:42 UTC 
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.2 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.