Bug 1709938

Summary:	HE deployment fail with 'Not enough memory' when given the engine vm the maximum memory
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ido Rosenzwig <irosenzw>
Component:	cockpit-ovirt	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED ERRATA	QA Contact:	Wei Wang <weiwang>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.1	CC:	bugs, cshao, dfediuck, huzhao, lsvaty, mavital, mgoldboi, nlevy, qiyuan, sbonazzo, weiwang, yaniwang, yturgema
Target Milestone:	ovirt-4.3.5	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1709015	Environment:
Last Closed:	2019-08-12 11:53:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1709015
Bug Blocks:

Description Ido Rosenzwig 2019-05-14 15:13:51 UTC

+++ This bug was initially created as a clone of Bug #1709015 +++

This bug was initially created as a copy of Bug #1704323

I am copying this bug because: 



Description of problem:
When deploying HE and giving the engine vm the max available memory it is sometimes fails with the following error because the system is using a little bit of the memory that was supposed to be assigned to the engine vm.

[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail if user chose more memory then the available memory]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Not enough memory: 4351MB, while only 4343MB are available on the host"}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes - not always

Steps to Reproduce:
1. deploy hosted-engine
2. give the max available memory - the default
3.

Actual results:
deployment fail (sometimes)

Expected results:
deployment succeed

Additional info:
-

--- Additional comment from Wei Wang on 2019-05-14 02:55:49 UTC ---

Test Version
rhvh-4.3.0.6-0.20190418.0+1
cockpit-dashboard-176-4.el7.x86_64
cockpit-bridge-176-4.el7.x86_64
cockpit-storaged-176-4.el7.noarch
cockpit-176-4.el7.x86_64
cockpit-system-176-4.el7.noarch
cockpit-ws-176-4.el7.x86_64
cockpit-machines-ovirt-176-4.el7.noarch
cockpit-ovirt-dashboard-0.12.8-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.7-1.el7ev.noarch

Test Steps:
1. Clean install rhvh-4.3.0.6-0.20190418.0
2. deploy hosted-engine
   a: via cockpit UI
   b: via CLI

3. Set the max available memory

Result:
a. For cockpit UI, QE cannot reproduce this issue after trying 5 times
b. For CLI, QE cannot reproduce this issue after trying 5 times

So QE cannot reproduce this issue, maybe I missing some key steps? Could you please give me some points? thanks!

--- Additional comment from Ido Rosenzwig on 2019-05-14 06:08:22 UTC ---

as I mentioned, it happens sometimes.
On the CLI no amount of memory was reserved for the host while on cockpit we reserved in the past 256MB.
Thus, it is more likely that you will succeed reproducing it via CLI and not via cockpit UI.

The Fix was to reserve 512MB on the host. That's why we have a patch in cockpit-ovirt too.

Comment 2 Wei Wang 2019-05-23 12:59:01 UTC

Test Version
RHVH-4.3-20190523.0-RHVH-x86_64-dvd1.iso
cockpit-ovirt-dashboard-0.13.0-1.el7ev.noarch

Test steps:
1. Clean install RHVH-4.3-20190523.0-RHVH-x86_64-dvd1.iso
2. Deploy hosted-engine via CLI
3. Set the max available memory(Get from cockpit wizard)

Result:
Deploy failed
[ INFO  ] TASK [ovirt.hosted_engine_setup : Fail if user chose more memory then the available memory]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Not enough memory! 62891MB, while only 62788MB are available on the host. Be aware that 512MB is reserved for the host and cannot be allocated to the engine VM."}
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook
[ INFO  ] Stage: Clean up


Move bug status to "ASSIGNED"

Comment 5 Wei Wang 2019-06-13 00:24:51 UTC

QE will do it until getting the build.

Comment 6 Wei Wang 2019-06-21 11:14:18 UTC

Test Version
RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso
cockpit-system-195-1.el7.noarch
cockpit-195-1.el7.x86_64
cockpit-bridge-195-1.el7.x86_64
cockpit-ws-195-1.el7.x86_64
cockpit-machines-ovirt-195-1.el7.noarch
cockpit-dashboard-195-1.el7.x86_64
cockpit-storaged-195-1.el7.noarch
cockpit-ovirt-dashboard-0.13.2-2.el7ev.noarch

Test Steps:
According to comment 0

Result:
Hosted engine deploys successfully

bug is fixed, verified.

Comment 8 errata-xmlrpc 2019-08-12 11:53:51 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/RHSA-2019:2433