Bug 1071200

Summary: CpuOverCommitDurationMinutes limited to a single digit value by regular expression in database scripts
Product: [Retired] oVirt Reporter: Jiri Moskovcak <jmoskovc>
Component: ovirt-engine-webadminAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, bazulay, dfediuck, ecohen, gklein, iheim, jentrena, jmoskovc, mgoldboi, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.4.1   
Hardware: All   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1070704 Environment:
Last Closed: 2014-05-08 13:37:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1070704    

Description Jiri Moskovcak 2014-02-28 09:05:36 UTC
+++ 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):

How reproducible:

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.

Comment 1 Itamar Heim 2014-03-02 05:42:25 UTC
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.

Comment 2 Sandro Bonazzola 2014-03-04 09:29:25 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Sandro Bonazzola 2014-05-08 13:37:40 UTC
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.