Bug 1565627

Summary: VM brq-openstack is down with error. Exit message: XML error: both maximum memory size and memory slot count must be specified.
Product: [oVirt] ovirt-engine Reporter: Jiri Belka <jbelka>
Component: Backend.CoreAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.2.6CC: bugs, jbelka, michal.skrivanek
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-16 13:00:37 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:

Description Jiri Belka 2018-04-10 12:56:25 UTC
Description of problem:

the vm was started on 4.1 cluster and cannot be started on 4.2 because of:


it seems there's odd max memory:

-[ RECORD 1 ]------------------+----------------------------------------------------------------------------------------
vm_name                        | brq-openstack
mem_size_mb                    | 2048
max_memory_size_mb             | 4194304

(also visible in admin portal)

changing max memory in admin portal solved the issue:

-[ RECORD 1 ]------------------+----------------------------------------------------------------------------------------
vm_name                        | brq-openstack
mem_size_mb                    | 2048
max_memory_size_mb             | 16384



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

How reproducible:
1 in 1

Steps to Reproduce:
1. 
2.
3.

Actual results:
a vm which got started in time of 4.1 cluster cannot run on 4.2 env now

Expected results:
should work

Additional info:

Comment 2 Yaniv Kaul 2018-04-11 06:34:00 UTC
Dup of https://bugzilla.redhat.com/show_bug.cgi?id=1557272 ?

Comment 3 Jiri Belka 2018-04-11 06:46:17 UTC
(In reply to Yaniv Kaul from comment #2)
> Dup of https://bugzilla.redhat.com/show_bug.cgi?id=1557272 ?

Seems so, so after one month we still have the issue here.

Comment 4 Michal Skrivanek 2018-04-16 13:00:37 UTC

*** This bug has been marked as a duplicate of bug 1557272 ***