Bug 2079605

Summary: Not pinned numa nodes configuration is cleared after export/import from OVA
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5.0.4CC: ahadas, bugs, dfodor, emarcus, nkoenig
Target Milestone: ovirt-4.5.1Flags: 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:
Attachments:
Description Flags
engine log none

Description Polina 2022-04-27 21:02:01 UTC
Created attachment 1875492 [details]
engine log

Description of problem:
Not pinned numanodes numbe must not be cleared while OVA exporting/importing 

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

How reproducible:100%


Steps to Reproduce:
1. Configure VM with numa nodes number according to the host numa topology (2 or 4)
2. Export to OVA
3. Remove the VM and import it from the saved OVA file

Actual results:
The VM has zero numa nodes

Expected results:configured numa nodes number must be saved after after export/import as OVA


Additional info:

Comment 1 Arik 2022-05-02 11:32:10 UTC
More important now with the introduction of dedicated CPUs where we expect users to specify the amount of numa nodes

Comment 2 Polina 2022-06-19 11:24:37 UTC
verified on ovirt-engine-4.5.1.2-0.11.el8ev.noarch according to described scenario.

Comment 3 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.