+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1433961 +++ ====================================================================== 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 (Originally by Martin Sivak)
Checked on rhevm-3.6.11-0.1.el6.noarch Send POST request to the engine: <cluster> <name>overcommit-mburman</name> <cpu id="Intel Conroe Family"/> <data_center id="00000001-0001-0001-0001-0000000002e0"/> <version major="3" minor="6"/> </cluster> Response: <fault> <reason>Operation Failed</reason> <detail>[KSM or balooning must be enabled to allow memory optimization.]</detail> </fault>
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [TAG 'ovirt-engine-3.6.11' DOESN'T CONTAIN PATCH 'https://gerrit.ovirt.org/74826'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-3.6.11 For more info please contact: rhv-devops
Checked on rhevm-3.6.11-0.2.el6.noarch Bug still exists POST request: <cluster> <name>test</name> <data_center id="00000001-0001-0001-0001-000000000298" /> <cpu id="Intel Conroe Family"/> </cluster> POST response: <fault> <reason>Operation Failed</reason> <detail>[KSM or balooning must be enabled to allow memory optimization.]</detail> </fault>
The 3.6 engine build was accidentally done from an old tag. There will be a new one tomorrow...
Verified on rhevm-3.6.11.1-0.1.el6.noarch
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:1210