Bug 784206 - [TEXT] Wrong warning messages after installation if machine has less than 4 GB RAM
Summary: [TEXT] Wrong warning messages after installation if machine has less than 4 G...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.1
Assignee: Alex Lourie
QA Contact:
URL:
Whiteboard:
: 795062 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 09:23 UTC by Jakub Libosvar
Modified: 2012-08-09 08:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Jakub Libosvar 2012-01-24 09:23:44 UTC
Description of problem:
If ovirt-engine is installed on machine with less than 4GB, after successful installation a message appears:

 * There is less than 4 GB available free memory on the Host.
It is  recommended to have at least 4 GB available memory to run the RHEV Manager.

In the second line - I don't want to run RHEV Manager but oVirt.

Also the first line seems a little bit misleading since I have no Host set up yet, I would go with something like "..memory on this machine" or so.

Version-Release number of selected component (if applicable):
ovirt-engine-3.0.0_0001-1.3.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install ovirt-engine on machine with less than 4GB RAM

Comment 1 Alex Lourie 2012-01-30 10:52:48 UTC
Updated text to more clear one. Also, reference to RHEV was removed.

Comment 2 Alex Lourie 2012-03-20 10:13:11 UTC
*** Bug 795062 has been marked as a duplicate of this bug. ***

Comment 3 Itamar Heim 2012-08-09 08:03:41 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/

Comment 4 Itamar Heim 2012-08-09 08:04:17 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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