Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1213134

Summary: Add GB information to SD percentage threshold on edit and general tab
Product: [Retired] oVirt Reporter: Vered Volansky <vered>
Component: ovirt-engine-webadminAssignee: Vered Volansky <vered>
Status: CLOSED CURRENTRELEASE QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6CC: amureini, bugs, ecohen, gklein, lsurette, mgoldboi, ogofen, rbalakri, tnisan, yeylon, ylavi
Target Milestone: m1   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:38:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1185839    
Bug Blocks:    

Description Vered Volansky 2015-04-19 08:41:31 UTC 
After adding what's currently called Storage Domain thresholds-
When editing a storage domain, the percentage threshold (currently called "Low S[ace Threshold") should also display in brackets the GB information.
For instance, If a 100GB SD is set to 10% threshold, 10GB should appear in brackets.
Comment 1 Max Kovgan 2015-06-28 14:12:43 UTC 
ovirt-3.6.0-3 release
Comment 2 Kevin Alon Goldblatt 2015-07-08 10:50:03 UTC 
Verified with Version:
--------------------------------------
vdsm-4.17.0-1054.git562e711.el7.noarchrpm -qa 
ovirt-engine-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch


Verified with the following scenario:
--------------------------------------
1. Storage Tab - Edit Storage Domain -> Advanced Parameters 
>>>> Displays the following: "Warning Low Space Indicator(%) |10| 12G

Verified on a Nested Host!
Moving to VERIFIED!
Comment 3 Sandro Bonazzola 2015-11-04 11:38:56 UTC 
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.