Bug 1073776

Summary: CpuOverCommitDurationMinutes limited to a single digit value by regular expression in database scripts
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engine-webadmin-portalAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: acathrow, adahms, bazulay, dfediuck, ecohen, gchaplik, iheim, jmoskovc, mavital, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 3.3.2   
Hardware: All   
OS: Linux   
Whiteboard: sla
Fixed In Version: is35 Doc Type: Bug Fix
Doc Text:
Previously, it was not possible to set the value of the CpuOverCommitDurationMinutes key to a value greater than '9'. This was caused by the range of possible values only allowing a single character to be input. Now, the range of possible values for this key has been expanded so that a maximum of two characters can be specified.
Story Points: ---
Clone Of: 1070704 Environment:
Last Closed: 2014-04-09 17:56:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1070704    
Bug Blocks:    

Comment 1 Jiri Moskovcak 2014-03-10 12:03:36 UTC
The patch has been merged.

Comment 3 Artyom 2014-03-17 10:17:59 UTC
Verified on is35

Comment 4 Zac Dover 2014-04-03 02:26:50 UTC
This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 6 errata-xmlrpc 2014-04-09 17:56:25 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-0384.html