Bug 2079605 - Not pinned numa nodes configuration is cleared after export/import from OVA
Summary: Not pinned numa nodes configuration is cleared after export/import from OVA
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.5.0.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.5.1
: ---
Assignee: Liran Rotenberg
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-27 21:02 UTC by Polina
Modified: 2022-06-23 05:54 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.5.1.2
Clone Of:
Environment:
Last Closed: 2022-06-23 05:54:58 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?

Attachments (Terms of Use)
engine log (181.55 KB, application/gzip)
2022-04-27 21:02 UTC, Polina 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 387 0 None Draft Add NUMA nodes to OVA 2022-05-26 13:39:33 UTC
Red Hat Issue Tracker RHV-45879 0 None None None 2022-04-27 21:09:06 UTC

Internal Links: 2083679

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.
Note You need to log in before you can comment on or make changes to this bug.