Bug 1435954

Summary: Change the default value for the cluster over commitment to 100
Product: [oVirt] ovirt-engine Reporter: Artyom <alukiano>
Component: RestAPIAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, dfediuck, ncredi
Target Milestone: ---Keywords: Automation, Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-27 06:40:38 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 Artyom 2017-03-26 07:20:26 UTC 
Description of problem:
Adding the cluster response
<cluster>
    <name>golden_env_mixed_2</name>
    <cpu id="Intel Conroe Family"/>
    <data_center id="f56afe09-7b32-4436-8e57-da3a04794a7c"/>
</cluster>

fails with the error
<fault>
<reason>Operation Failed</reason>
<detail>[KSM or balooning must be enabled to allow memory optimization.]</detail>
 </fault>

Version-Release number of selected component (if applicable):
rhevm-3.6.11-0.1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create the cluster with the body above
2.
3.

Actual results:
<fault>
<reason>Operation Failed</reason>
<detail>[KSM or balooning must be enabled to allow memory optimization.]</detail>
 </fault>

Expected results:
Request succeeds without any errors and cluster created.

Additional info:
W/A <cluster>
    <name>golden_env_mixed_2</name>
    <cpu id="Intel Conroe Family"/>
    <data_center id="f56afe09-7b32-4436-8e57-da3a04794a7c"/>
    <version major="3" minor="6"/>
  	<memory_policy>
		<overcommit percent="100" />
 	</memory_policy>
</cluster>
Comment 1 Nelly Credi 2017-03-26 07:25:19 UTC 
Removing auto blocker since there is a WA
Comment 2 Doron Fediuck 2017-03-27 06:40:38 UTC 

*** This bug has been marked as a duplicate of bug 1433961 ***