Bug 1339640 - scheduling policy overcommitminduration is not editable
Summary: scheduling policy overcommitminduration is not editable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.0.2
: 4.0.2.4
Assignee: Martin Sivák
QA Contact: Eldad Marciano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 13:57 UTC by Eldad Marciano
Modified: 2016-08-12 14:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: An overcommit duration value was missing from the list of editable values for evenly and powersaving balancing policy units. Consequence: The overcommit duration was not editable in the scheduling policy dialogs. Fix: The value was added to the list. Result: Overcommit duration can now be configured again.
Clone Of:
Environment:
Last Closed: 2016-08-12 14:30:47 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
msivak: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
screen shot of the drop down list (54.53 KB, image/png)
2016-05-25 14:05 UTC, Eldad Marciano 		no flags Details
RHEVM-4.0-Policies (67.51 KB, image/png)
2016-07-20 09:00 UTC, Yuri Obshansky 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58064 0 master MERGED sla: Mark CPU_OVERCOMMIT_DURATION as editable in balancing units 2016-05-26 18:34:23 UTC
oVirt gerrit 61094 0 ovirt-engine-4.0 MERGED sla: Mark CPU_OVERCOMMIT_DURATION as editable in balancing units 2016-07-25 11:15:45 UTC
oVirt gerrit 61293 0 ovirt-engine-4.0.2 MERGED sla: Mark CPU_OVERCOMMIT_DURATION as editable in balancing units 2016-07-26 15:03:42 UTC

Description Eldad Marciano 2016-05-25 13:57:14 UTC 
Description of problem:
usally the scale team using 
HighUtilzaion and CpuOverCommitMinDurratoin for distribute vms
seems like 
CpuOverCommitMinDurratoin is not editable anymore

Version-Release number of selected component (if applicable):
4.0 alpha releease

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Eldad Marciano 2016-05-25 14:05:31 UTC 
Created attachment 1161440 [details]
screen shot of the drop down list

adding screen shot, see that cpuovercommitminduration is missing in the dropdown list
Comment 2 Eldad Marciano 2016-05-25 14:24:28 UTC 
requesting merge this patch to the next 4.0 zstream
Gil could you ack this one?
Comment 3 Red Hat Bugzilla Rules Engine 2016-05-25 14:24:32 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 4 Red Hat Bugzilla Rules Engine 2016-05-25 16:07:13 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 5 Yuri Obshansky 2016-07-20 09:00:06 UTC 
Bug verified on RHEVM 4.0.2-0.2.rc1.el7ev
Property CpuOverCommitMinDurratoin still doesn't exist in drop down list.
See attached screenshot RHEVM-4.0-Policies
Status changed to NEW

Yuri
Comment 6 Red Hat Bugzilla Rules Engine 2016-07-20 09:00:11 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 7 Yuri Obshansky 2016-07-20 09:00:45 UTC 
Created attachment 1181968 [details]
RHEVM-4.0-Policies
Comment 8 Roy Golan 2016-07-20 10:40:49 UTC 
somehow missed the branch

git branch -r --contains 85e7cf4acfdb8e05ccfbb1108879f436087108d4
origin/master

only needs cherry-picking
Comment 10 Gil Klein 2016-07-27 14:51:31 UTC 
Failed QA based on comment #9
Comment 11 Martin Sivák 2016-07-28 11:24:15 UTC 
Because the patch is not part of the build and the bot moved it to ON_QA by mistake.
Comment 12 Eldad Marciano 2016-07-31 12:53:48 UTC 
verified on top of rhevm-4.0.2.2-0.1.el7ev.noarch
Note You need to log in before you can comment on or make changes to this bug.