Bug 1544735

Summary: Gluster-block does not understand PVC's storage unit
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Humble Chirammal <hchiramm>
Component: heketiAssignee: Michael Adam <madam>
Status: CLOSED ERRATA QA Contact: Rachael <rgeorge>
Severity: medium Docs Contact:
Priority: medium    
Version: rhgs-3.0CC: aos-bugs, aos-storage-staff, hchiramm, jcall, jhou, lxia, madam, mliyazud, pprakash, rcyriac, rhs-bugs, storage-qa-internal, tlarsson
Target Milestone: ---   
Target Release: CNS 3.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1505290
: 1544743 (view as bug list) Environment:
Last Closed: 2018-04-05 03:08:10 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:
Embargoed:
Bug Depends On: 1505290    
Bug Blocks: 1526414, 1537461, 1544743    

Comment 2 Humble Chirammal 2018-02-13 12:12:41 UTC 
https://github.com/heketi/heketi/pull/935
Comment 4 Rachael 2018-03-12 14:19:14 UTC 
Given below is the summary of how different storage units are handled 

1. When the storage unit in the PVC is specified as 'Gi', the PV provisioned is of the exact size as specified.

2. When the storage unit in the PVC is specified as 'G', the value is converted in terms of 'Gi' and the PV is provisioned accordingly 

3. When no storage unit is specified the value is taken in bytes and rounded up to the nearest GiB value. 

Detailed explanation can be found in https://bugzilla.redhat.com/show_bug.cgi?id=1505290

Hence moving the bug to verified
Comment 8 errata-xmlrpc 2018-04-05 03:08:10 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.

https://access.redhat.com/errata/RHEA-2018:0638