Bug 1559042

Summary:	Remove disk and memory check flags from the OpenShift ansible-inventory files
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Shirly Radco <sradco>
Component:	Generic	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1.3.1	CC:	bugs, lveyde
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	1.1.3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-metrics-1.1.3.4-1.el7ev	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-18 12:26:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1475135

Description Shirly Radco 2018-03-21 15:08:15 UTC

Description of problem:

Remove disk and memory check flags from the OpenShift ansible-inventory files,
Users should setup the machine based on the OpenShift master Minimum Hardware Requirements:
https://docs.openshift.org/latest/install_config/install/prerequisites.html#hardware.

Currently file include a less restrict requirements:
openshift_check_min_host_memory_gb=7
openshift_check_min_host_disk_gb=14

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

How reproducible:
100%

Steps to Reproduce:
1.Set memory to lower than 7G RAM or /var to less then 14GB.
2.Install OpenShift
3.

Actual results:
Openshift fails on memory lower then 7G or /var less then 14GB.

Expected results:
OpenShift ansible should fail on requirements based on the values for master in https://docs.openshift.org/latest/install_config/install/prerequisites.html#hardware.

Additional info:

Comment 1 Lukas Svaty 2018-04-16 14:31:08 UTC

default options are used,
verified in ovirt-engine-metrics-1.1.4-0.0.master.20180408064245.el7.centos.noarch

Comment 2 Sandro Bonazzola 2018-04-18 12:26:50 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

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