Bug 1530607

Summary:	[downstream clone - 4.1.9] HE VM can't start because incorrect value under vm.conf file
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-hosted-engine-ha	Assignee:	Martin Sivák <msivak>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	alukiano, bugs, eheftman, lsurette, mavital, ykaul, ylavi
Target Milestone:	ovirt-4.1.10	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1524331	Environment:
Last Closed:	2018-03-20 16:36:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1524331
Bug Blocks:

Description rhev-integ 2018-01-03 13:28:11 UTC

+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1524331 +++
======================================================================

Description of problem:
We put incorrect values under vm.conf file
cat /var/run/ovirt-hosted-engine-ha/vm.conf
...
memSize=2
...
so when we start HE VM we have only 2 MiB of memory
...
<memory unit='KiB'>2048</memory>
...

Version-Release number of selected component (if applicable):
# rpm -qa | grep hosted
ovirt-hosted-engine-ha-2.2.0-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.0-2.el7ev.noarch

ovirt-engine-4.2.0-0.6.el7.noarch


How reproducible:
Always

Steps to Reproduce:
1. Deploy hosted-engine environment
2. On one of HE hosts check /var/run/ovirt-hosted-engine-ha/vm.conf
3.

Actual results:
I see a very small amount of VM memory that different from one that I specified on deployment.

Expected results:
It must have correct value for VM memory

Additional info:
I do not sure that bug connects to initial deployment or to OVF generation.

(Originally by Artyom Lukianov)

Comment 1 rhev-integ 2018-01-03 13:28:16 UTC

Can you attach the vm.conf and the ovf please?

(Originally by Martin Sivak)

Comment 3 rhev-integ 2018-01-03 13:28:19 UTC

I checked agent.log with DEBUG and looks that OVF is fine
<Item>
  <rasd:Caption>5120 MB of memory</rasd:Caption>
  <rasd:Description>Memory Size</rasd:Description>
  <rasd:InstanceId>2</rasd:InstanceId>
  <rasd:ResourceType>4</rasd:ResourceType>
  <rasd:AllocationUnits>MegaBytes</rasd:AllocationUnits>
  <rasd:VirtualQuantity>5120</rasd:VirtualQuantity>
</Item>

(Originally by Artyom Lukianov)

Comment 4 rhev-integ 2018-01-03 13:28:23 UTC

Verified on ovirt-hosted-engine-ha-2.2.1-1.el7ev.noarch

(Originally by Artyom Lukianov)

Comment 5 rhev-integ 2018-01-03 13:28:26 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

(Originally by Sandro Bonazzola)

Comment 7 Martin Sivák 2018-01-17 11:14:15 UTC

This is only happening when 4.1 hosted engine hosts are used with 4.2 engine. That is a supported case and it needs to work.

Comment 9 Artyom 2018-02-19 16:39:24 UTC

Verified on ovirt-hosted-engine-ha-2.1.9-1.el7ev.noarch

Comment 13 errata-xmlrpc 2018-03-20 16:36:48 UTC

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:0561

Comment 14 Franta Kust 2019-05-16 13:06:16 UTC

BZ<2>Jira Resync