Back to bug 1402838

Who When What Removed Added
Julio Entrena Perez 2016-12-08 12:49:52 UTC CC jentrena
Doron Fediuck 2016-12-08 12:54:14 UTC Target Milestone --- ovirt-4.1.0-beta
Doron Fediuck 2016-12-08 12:59:57 UTC Assignee nobody jtokar
Target Milestone ovirt-4.1.0-beta ovirt-3.6.9
Yaniv Lavi 2016-12-08 13:11:00 UTC CC ydary
Target Milestone ovirt-3.6.9 ovirt-3.6.10
Doron Fediuck 2016-12-08 13:28:01 UTC Target Milestone ovirt-3.6.10 ovirt-3.6.11
Yaniv Lavi 2016-12-11 14:44:36 UTC CC ydary
Moran Goldboim 2016-12-14 11:15:49 UTC Priority unspecified high
CC mgoldboi
meital avital 2016-12-14 11:16:37 UTC QA Contact mavital mshira
Paul Dwyer 2016-12-14 11:24:47 UTC CC pdwyer
Julio Entrena Perez 2016-12-14 12:34:17 UTC Link ID Red Hat Knowledge Base (Solution) 2808171
Jenny Tokar 2017-02-28 15:29:52 UTC Status NEW ASSIGNED
Martin Sivák 2017-03-13 10:09:27 UTC Blocks 1427844
Keywords ZStream
Target Milestone ovirt-3.6.11 ovirt-4.1.2
Link ID oVirt gerrit 73558
Status ASSIGNED POST
Link ID oVirt gerrit 73649
Status POST MODIFIED
Jenny Tokar 2017-03-15 10:14:24 UTC Doc Text Cause:
the engine allowed setting over commitment without enabling KSM or ballooning.

Consequence:
scheduler will use the requested optimization, although there's nothing to allow this at the host level.

Fix:
disable setting over commitment without enabling KSM or ballooning.

Result:
over commitment can only be set when KSM or ballooning is enabled.
Doc Type If docs needed, set a value Bug Fix
errata-xmlrpc 2017-03-17 14:35:42 UTC Status MODIFIED ON_QA
Shira Maximov 2017-03-20 13:52:01 UTC Status ON_QA MODIFIED
errata-xmlrpc 2017-03-23 09:40:56 UTC Status MODIFIED ON_QA
Shira Maximov 2017-03-29 09:03:38 UTC Status ON_QA MODIFIED
errata-xmlrpc 2017-03-31 10:43:15 UTC Status MODIFIED ON_QA
Shira Maximov 2017-04-03 13:30:51 UTC Status ON_QA ASSIGNED
Martin Sivák 2017-04-05 10:16:22 UTC Status ASSIGNED MODIFIED
errata-xmlrpc 2017-04-26 12:57:23 UTC Status MODIFIED ON_QA
Shira Maximov 2017-04-26 14:08:14 UTC Status ON_QA VERIFIED
Tahlia Richardson 2017-05-12 05:29:08 UTC CC trichard
Doc Text Cause:
the engine allowed setting over commitment without enabling KSM or ballooning.

Consequence:
scheduler will use the requested optimization, although there's nothing to allow this at the host level.

Fix:
disable setting over commitment without enabling KSM or ballooning.

Result:
over commitment can only be set when KSM or ballooning is enabled.
Previously, the Manager allowed setting memory overcommitment without also enabling KSM or ballooning. The scheduler then used the requested optimization, but there was nothing allowing it at the host level. This has now been fixed so that memory overcommitment can only be set when KSM or ballooning is enabled.
errata-xmlrpc 2017-05-23 00:57:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-05-24 11:22:00 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-05-24 07:22:00 UTC
Gil Klein 2019-04-28 13:33:07 UTC CC gklein
Red Hat One Jira (issues.redhat.com) 2021-08-30 12:26:08 UTC Link ID Red Hat Issue Tracker RHV-35704

Back to bug 1402838