Bug 1351556
Summary: | LowUtiliztion parameter does not exist under power_saving policy | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
Component: | Backend.Core | Assignee: | Jenny Tokar <jtokar> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.0.0 | CC: | bugs, mgoldboi, rgolan | ||||
Target Milestone: | ovirt-4.0.2 | Keywords: | Regression, Triaged, ZStream | ||||
Target Release: | 4.0.2 | Flags: | rule-engine:
ovirt-4.0.z+
rule-engine: blocker+ mgoldboi: planning_ack+ rgolan: devel_ack+ mavital: testing_ack+ |
||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause:
LowUtilization parameter was removed from PowerSavingBalancePolicyUnit
Consequence:
Users were unable to set the low utilization parameter for power saving policy
Fix:
LowUtilization parameter was returned to PowerSavingBalancePolicyUnit
Result:
Users are able to set the low utilization parameter for power saving policy
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-08-12 14:25:51 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: | |||||||
Attachments: |
|
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. This bug was already fixed for master, adding ZStream keyword. Verified on rhevm-4.0.2-0.1.rc.el7ev.noarch |
Created attachment 1174475 [details] screenshot Description of problem: LowUtiliztion parameter does not exist under power_saving policy Version-Release number of selected component (if applicable): rhevm-4.0.0.6-0.1.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Change cluster scheduling policy to power_saving 2. Check power_saving policy parameters 3. Actual results: LowUtiliztion parameter does not exist Expected results: LowUtilization exists under power_saving policy Additional info: