+++ This bug was initially created as a clone of Bug #1070704 +++
Description of problem:
Can not set 'CpuOverCommitDurationMinutes' to a value higher than 9 neither through webadmin nor through the API.
Version-Release number of selected component (if applicable):
rhevm-dbscripts-3.3.0-0.46.el6ev
How reproducible:
Always
Steps to Reproduce:
1. Upgrade RHEV-M to 3.3.
2. Select a cluster running in compatibility version 3.3.
3. Edit --> Cluster Policy --> Select policy --> Evenly_Distributed
4. Try to set a value of 10 or higher for CpuOverCommitDurationMinutes and click OK.
Actual results:
Value field is flagged in red colour, can not commit desired value.
Expected results:
As per table 4.4 at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Administration_Guide/Cluster_general_entities.html :
"Maximum two characters. "
Additional info:
After migration, trying to raise compatibility version of a cluster where CpuOverCommitDurationMinutes >= 10 to version 3.3 fails.
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.
This is an automated message
oVirt 3.4.1 has been released:
* should fix your issue
* should be available at your local mirror within two days.
If problems still persist, please make note of it in this bug report.