Bug 1433961

Summary:	Disable overcommit by default when creating new cluster
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Martin Sivák <msivak>
Component:	ovirt-engine	Assignee:	Martin Sivák <msivak>
Status:	CLOSED ERRATA	QA Contact:	Shira Maximov <mshira>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.10	CC:	alukiano, dfediuck, eheftman, lsurette, mgoldboi, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	ovirt-4.1.2	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	Previously, it was possible to configure memory overcommit without setting memory ballooning or KSM control. This configuration affected the scheduling, but the memory was not freed. This has now been fixed by disabling ballooning and KSM by default, and setting memory optimization to “None” (100%).	Story Points:	---
Clone Of:
Clones:	1434013 (view as bug list)		Environment:
Last Closed:	2017-05-24 11:22:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Sivák 2017-03-20 13:18:55 UTC

Description of problem:

Currently new clusters have ballooning and KSM disabled by default and overcommit set to 200% by default.

Configuring overcommit without ballooning or KSM does not make any sense. It will affect scheduling (the engine will think it has more memory), but nothing will actually free the memory.

A recent change introduced a check for this situation, but we forgot to change the default value.

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

3.6.11, 4.1.2 and master branch as of 20th of March

How reproducible:

Always

Steps to Reproduce:
1. Create a cluster using REST API providing only name

Actual results:

407 Conflict - it is not possible to enable overcommit without ballooning or KSM

Expected results:

OK - cluster created with all ballooning, KSM and overcommit disabled

Additional info:

We tested a workaround using Python SDK to verify a cluster can be created when the overcommit value is provided:

https://gerrit.ovirt.org/#/c/74303/1

Comment 4 Doron Fediuck 2017-03-27 06:40:38 UTC

*** Bug 1435954 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2017-05-24 11:22:20 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2017:1280