Bug 1433961 – Disable overcommit by default when creating new cluster

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1433961 - Disable overcommit by default when creating new cluster

Summary:	Disable overcommit by default when creating new cluster

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.6.10
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	ovirt-4.1.2
Target Release:	---
Assigned To:	Martin Sivák
QA Contact:	Shira Maximov
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Duplicates:	1435954 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-20 09:18 EDT by Martin Sivák
Modified:	2017-05-24 07:22 EDT (History)
CC List:	10 users (show)

See Also:
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 07:22:20 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	74312	master	MERGED	core: Use no overcommit as the default cluster memory policy	2017-03-20 10:35 EDT
oVirt gerrit	74313	ovirt-engine-4.1	MERGED	core: Use no overcommit as the default cluster memory policy	2017-03-20 17:28 EDT
oVirt gerrit	74825	master	MERGED	core: New cluster has disabled overcommit by default (for real now)	2017-03-29 10:12 EDT
oVirt gerrit	74833	ovirt-engine-4.1	MERGED	core: New cluster has disabled overcommit by default (for real now)	2017-03-29 11:11 EDT
Red Hat Product Errata	RHEA-2017:1280	normal	SHIPPED_LIVE	Red Hat Virtualization Manager (ovirt-engine) 4.1.2	2017-05-24 11:18:48 EDT

Groups: None (edit)

Description Martin Sivák 2017-03-20 09:18:55 EDT

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 02:40:38 EDT

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

Comment 8 errata-xmlrpc 2017-05-24 07:22:20 EDT

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

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