Bug 1704323 - HE deployment fail with 'Not enough memory' when given the engine vm the maximum memory
Summary: HE deployment fail with 'Not enough memory' when given the engine vm the maxi...
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.4
: 2.3.8
Assignee: Ido Rosenzwig
QA Contact: Nikolai Sednev
Depends On:
Blocks: 1709969
TreeView+ depends on / blocked
Reported: 2019-04-29 14:46 UTC by Ido Rosenzwig
Modified: 2019-06-11 06:25 UTC (History)
3 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.3.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-11 06:25:44 UTC
oVirt Team: Integration
sbonazzo: ovirt-4.3?
sbonazzo: planning_ack?
sbonazzo: devel_ack+
sbonazzo: testing_ack?

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-ansible-hosted-engine-setup pull 185 0 None None None 2019-05-12 15:52:27 UTC
oVirt gerrit 99930 0 master MERGED Reserve small amount of memory for the host during deployment 2019-05-13 08:09:19 UTC
oVirt gerrit 99937 0 ovirt-hosted-engine-setup-2.3 MERGED Reserve small amount of memory for the host during deployment 2019-05-13 08:09:02 UTC

Description Ido Rosenzwig 2019-04-29 14:46:09 UTC
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

Actual results:
deployment fail (sometimes)

Expected results:
deployment succeed

Additional info:

Comment 1 Nikolai Sednev 2019-05-26 14:20:32 UTC
Works for me on these components on host with 32GB RAM, while deployed engine using 4GB RAM over NFS:
Software Version:
rhvm-appliance.x86_64 2:4.3-20190522.0.el7
Linux 3.10.0-957.12.2.el7.x86_64 #1 SMP Fri Apr 19 21:09:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)

Forth to https://www.ovirt.org/documentation/install-guide/chap-System_Requirements.html and Ido's recommendations, I used described above environment and moving this bug to verified as deployment succeeded.
In case that you have any other issues, please open separate bug with full description of the issue.

Comment 2 Sandro Bonazzola 2019-06-11 06:25:44 UTC
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE.

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

Note You need to log in before you can comment on or make changes to this bug.