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
*** Bug 1435954 has been marked as a duplicate of this bug. ***
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