+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1519811 +++ ====================================================================== Description of problem: During upgrade from RHEV-3 to RHV-4, the cluster compatibility level can't be increased, as some VMs show inconsistency in definition of max_memory_size_mb mem_size_mb Version-Release number of selected component (if applicable): latest ovirt-engine How reproducible: always Steps to Reproduce: 1. Setup a VM with mem_size_mb and min_allocated_mem to '1572864' in RHEV 3.6 2. upgrade RHEV database to RHV 4.1 3. check memory configuration in database Actual results: [root@dbview ~]# /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select vm_name,mem_size_mb,min_allocated_mem,max_memory_size_mb from vm_static where mem_size_mb >= '1048576' order by vm_name" vm_name | mem_size_mb | min_allocated_mem | max_memory_size_mb ------------+-------------+-------------------+-------------------- testvm-111 | 1572864 | 1572864 | 1048576 ^^^^^^^ Expected results: [root@dbview ~]# /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select vm_name,mem_size_mb,min_allocated_mem,max_memory_size_mb from vm_static where mem_size_mb >= '1048576' order by vm_name" vm_name | mem_size_mb | min_allocated_mem | max_memory_size_mb ------------+-------------+-------------------+-------------------- testvm-111 | 1572864 | 1572864 | 1572864 ^^^^^^^ Additional info: (Originally by Steffen Froemer)
Looks like some hardcoded value here: 04_01_0640_add_max_memory_size_column.sql -- 1048576 is an old default from *MaxMemorySizeInMB config values SET max_memory_size_mb = LEAST(4 * mem_size_mb, 1048576); Should it actually read the current *MaxMemorySizeInMB? Seems to be set to 4TB in CL 3.6. (Originally by Germano Veit Michel)
I'm sure you have already figured it out, but for completeness, the workaround is to issue this sql which will fix it: update vm_static set max_memory_size_mb = mem_size_mb where mem_size_mb > max_memory_size_mb; (Originally by Tomas Jelinek)
is there any timeframe, when this patch will be available? I have another customer, who will be affected by this issue when performing the RHV upgrade in near future.
as you can see in the target milestone it is planned for 4.1.9
Thanks Michael. It should be the week, that I've missed that.
Verify with: ovirt-engine-4.1.9-0.2 Steps: 1. Setup a VM with mem_size_mb and min_allocated_mem to '1572864' in RHEV 3.6 2. upgrade RHEV database to RHV 4.1 3. check memory configuration in database Output: # /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select vm_name,mem_size_mb,min_allocated_mem,max_memory_size_mb from vm_static where mem_size_mb >= '1048576' order by vm_name"; vm_name | mem_size_mb | min_allocated_mem | max_memory_size_mb ------------+-------------+-------------------+-------------------- bz_upgrade | 1572864 | 1572864 | 1572864 (1 row)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0135
BZ<2>Jira re-sync