Bug 1524331

Summary:	HE VM can't start because incorrect value under vm.conf file
Product:	[oVirt] ovirt-hosted-engine-ha	Reporter:	Artyom <alukiano>
Component:	Agent	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	2.2.0	CC:	alukiano, bugs
Target Milestone:	ovirt-4.2.0	Keywords:	Triaged, ZStream
Target Release:	2.2.1	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1530607 (view as bug list)		Environment:
Last Closed:	2017-12-20 11:00:27 UTC	Type:	Bug
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:
Bug Blocks:	1458711, 1530607

Description Artyom 2017-12-11 09:42:11 UTC

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.

Comment 1 Martin Sivák 2017-12-11 10:10:16 UTC

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

Comment 2 Artyom 2017-12-11 11:21:07 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>

Comment 3 Artyom 2017-12-13 07:33:24 UTC

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

Comment 4 Sandro Bonazzola 2017-12-20 11:00:27 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.