Bug 1526448 - insufficient memory message should state how much memory is needed
Summary: insufficient memory message should state how much memory is needed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.1
: ---
Assignee: Phillip Bailey
QA Contact: Yihui Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 14:11 UTC by Sandro Bonazzola
Modified: 2018-02-12 11:51 UTC (History)
13 users (show)

Fixed In Version: cockpit-ovirt-0.11.5-0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:51:22 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.2+
mgoldboi: planning_ack+
msivak: devel_ack+
yzhao: testing_ack+


Attachments (Terms of Use)
screenshot (54.45 KB, image/png)
2017-12-15 14:11 UTC, Sandro Bonazzola
no flags Details
memory_limit1 (10.93 KB, image/png)
2018-01-18 05:58 UTC, Yihui Zhao
no flags Details
memory_limit2 (16.76 KB, image/png)
2018-01-18 06:06 UTC, Yihui Zhao
no flags Details
memory_no_warning (58.49 KB, image/png)
2018-01-18 06:12 UTC, Yihui Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85556 0 'None' 'MERGED' 'wizard: Modify handling of minimum memory requirements' 2019-12-04 07:27:26 UTC
oVirt gerrit 86285 0 'None' 'MERGED' 'wizard: Modify handling of minimum memory requirements' 2019-12-04 07:27:26 UTC

Description Sandro Bonazzola 2017-12-15 14:11:18 UTC
Created attachment 1368498 [details]
screenshot

Trying to deploy hosted-engine on a 4GB VM with nested VT.
The wizard showed: 
"There is insufficient memory available to support engine VM creation at this time!" See attachment.

The error should give an hint on the minimum amount of RAM needed for the wizard to work.

Comment 1 Yihui Zhao 2018-01-18 05:58:38 UTC
Created attachment 1382747 [details]
memory_limit1

Comment 2 Yihui Zhao 2018-01-18 05:59:44 UTC
Can reproduce.

Test version:
Host version : Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)
Guest version: rhvh-4.2.0.6-0.20180104.0+1(RHVH-4.2-20180104.0-RHVH-x86_64-dvd1.iso)

cockpit-storaged-155-1.el7.noarch
cockpit-ws-155-1.el7.x86_64
cockpit-dashboard-155-1.el7.x86_64
cockpit-155-1.el7.x86_64
cockpit-bridge-155-1.el7.x86_64
cockpit-system-155-1.el7.noarch
cockpit-ovirt-dashboard-0.11.3-0.1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.2-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.2-1.el7ev.noarch


Test steps:
1. Open the RHEL7.5 Nested function
2. Install a VM(RHVH 4.2 rhvh-4.2.0.6-0.20180104.0+1) on the RHEL7.5
3. Set the VM cpu-type is "host-passthrough", memory is "4GB"
4. Deploy HE on the VM(RHVH4.2) via cockpit


Test results:
After step4, cockpit shows that "There is insufficient memory available to support engine VM creation at this time!"

Attachments:
https://bugzilla.redhat.com/attachment.cgi?id=1382747

Comment 3 Yihui Zhao 2018-01-18 06:06:42 UTC
Created attachment 1382749 [details]
memory_limit2

Comment 4 Yihui Zhao 2018-01-18 06:12:27 UTC
Created attachment 1382750 [details]
memory_no_warning

Comment 5 Yihui Zhao 2018-01-18 06:14:13 UTC
Retest with the new RHVH version(rhvh-4.2.1.1-0.20180115.0+1), it seems ok.


Test version:
Host version : Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)
Guest version: rhvh-4.2.1.1-0.20180115.0+1

cockpit-ws-157-1.el7.x86_64
cockpit-dashboard-157-1.el7.x86_64
cockpit-bridge-157-1.el7.x86_64
cockpit-157-1.el7.x86_64
cockpit-storaged-157-1.el7.noarch
cockpit-system-157-1.el7.noarch
cockpit-ovirt-dashboard-0.11.4-0.1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.3-1.el7ev.noarch


Test steps:
1. Open the RHEL7.5 Nested function
2. Install a VM(RHVH 4.2 rhvh-4.2.1.1-0.20180115.0+1) on the RHEL7.5
3. Set the VM cpu-type is "host-passthrough", memory is "4GB"
4. Deploy HE on the VM(RHVH4.2) via cockpit


Test results:
After step4, cockpit shows that "The minimum recommended amount of memory is 4,096MB. Currently, only 3,360MB is available."


Attachment:
https://bugzilla.redhat.com/attachment.cgi?id=1382749


Additional info:
1. If the available memory arrive the 4096MB, there is no warning shows.
https://bugzilla.redhat.com/attachment.cgi?id=1382750


So, I will change the bug's status to VERIFIED if it arrives to ON_QA.

Comment 6 Yihui Zhao 2018-01-29 07:49:36 UTC
According to the comment 5, change the bug's status to verified.

Comment 7 Sandro Bonazzola 2018-02-12 11:51:22 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.