Bug 1704323
Summary: | HE deployment fail with 'Not enough memory' when given the engine vm the maximum memory | ||
---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Ido Rosenzwig <irosenzw> |
Component: | General | Assignee: | Ido Rosenzwig <irosenzw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | --- | CC: | bugs, nsednev, stirabos |
Target Milestone: | ovirt-4.3.4 | Keywords: | ZStream |
Target Release: | 2.3.8 | Flags: | sbonazzo:
ovirt-4.3?
sbonazzo: planning_ack? sbonazzo: devel_ack+ sbonazzo: testing_ack? |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-hosted-engine-setup-2.3.8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-11 06:25:44 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1709969 |
Description
Ido Rosenzwig
2019-04-29 14:46:09 UTC
Works for me on these components on host with 32GB RAM, while deployed engine using 4GB RAM over NFS: Software Version:4.3.4.1-0.1.el7 ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.8-1.el7ev.noarch 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. 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. |