Bug 1854041

Summary: [v2v] Warning message during every v2v import about incompatible parameter "memory"
Product: [oVirt] ovirt-engine Reporter: Beni Pelled <bpelled>
Component: GeneralAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.1.7CC: ahadas, bugs, nsimsolo
Target Milestone: ovirt-4.4.5Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.5.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-18 15:12:33 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
import_log none

Description Beni Pelled 2020-07-06 07:38:05 UTC 
Description of problem:
A warning message occurs during every v2v import from VMware (I didn't check with other providers):

2020-07-06 10:20:04,650+03 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-14568) [6a673ea1-f32d-487c-bb4b-e0b8c7a17d87] EVENT_ID: IMPORTEXPORT_IMPORT_VM_UPDATED(1,229), The imported VM automation_v2v_rhel_7_2_vmware was updated because these parameters were incompatible with selected cluster version: memory


Version-Release number of selected component (if applicable):
4.4.1.7-0.3.el8ev

How reproducible:
100%

Steps to Reproduce:
1. Import a VM from VMWare

Actual results:
The VM imported successfully with the same memory size (2048MB in my case) but there is a warning message 

Expected results:
No warning message

Additional info:
The engine and import logs attached.
Comment 1 Beni Pelled 2020-07-06 07:38:45 UTC 
Created attachment 1699992 [details]
engine.log
Comment 2 Beni Pelled 2020-07-06 07:39:14 UTC 
Created attachment 1699993 [details]
import_log
Comment 3 Arik 2020-07-06 09:15:20 UTC 
The memory size didn't change but the guaranteed memory and/or the max memory probably change.
Can you please check what were the values of MinAllocatedMem and MaxMemorySizeMb in the OVF that v2v generated?
Comment 4 Arik 2020-07-06 09:50:53 UTC 
Apparently there's no min guaranteed memory and no max memory in the OVF generated by virt-v2v
Warnings should be printed when we alter the VM configuration (compared to its original configuration) but don't make much sense in cases like this
Comment 5 Nisim Simsolo 2021-02-23 09:00:37 UTC 
Verified:
ovirt-engine-4.4.5.6-0.11.el8ev
vdsm-4.40.50.6-1.el8ev.x86_64
libvirt-daemon-6.6.0-13.module+el8.3.1+9548+0a8fede5.x86_64
virt-v2v-1.42.0-7.module+el8.3.1+9562+c3ede7c6.x86_64
qemu-kvm-5.1.0-20.module+el8.3.1+9918+230f5c26.x86_64
Comment 6 Sandro Bonazzola 2021-03-18 15:12:33 UTC 
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 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.