Bug 1505290
| Summary: | Gluster-block does not understand PVC's storage unit | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Jianwei Hou <jhou> | |
| Component: | kubernetes | Assignee: | Humble Chirammal <hchiramm> | |
| Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | rhgs-3.0 | CC: | aos-bugs, aos-storage-staff, asriram, hchiramm, jcall, jhou, lxia, madam, rcyriac, rgeorge, rhs-bugs, tlarsson | |
| Target Milestone: | --- | |||
| Target Release: | CNS 3.9 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Previously, the gluster-block provisioner did not identify the storage units correctly in the PVC. For example, it would identify 1 as 1GiB by default and the provisioner would fail on 1Gi. With this enhancement, gluster-block provisioner identifies the storage units correctly, ie, 1 will be treated as 1 byte, 1Gi will be treated as 1 GibiByte, and 1Ki will be treated as 1KibiByte.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1537461 1544735 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-05 03:25:59 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: | ||||
| Bug Blocks: | 1526414, 1537461, 1544735, 1544743 | |||
|
Description
Jianwei Hou
2017-10-23 08:34:07 UTC
Updates:
In 3.9, the actual capacity is 1Gi greater than wanted capacity when using a *glusterfs* provisioner. Replacing '1Gi' with '1' then it works correct.
# oc get pvc glusterfs -o yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
annotations:
pv.kubernetes.io/bind-completed: "yes"
pv.kubernetes.io/bound-by-controller: "yes"
volume.beta.kubernetes.io/storage-class: glusterfs
volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/glusterfs
creationTimestamp: 2018-01-05T02:40:52Z
name: glusterfs
namespace: storage-project
resourceVersion: "95634"
selfLink: /api/v1/namespaces/storage-project/persistentvolumeclaims/glusterfs
uid: d8c8e043-f1c1-11e7-9c0c-0050569f5abb
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
volumeName: pvc-d8c8e043-f1c1-11e7-9c0c-0050569f5abb
status:
accessModes:
- ReadWriteOnce
capacity:
storage: 2G
phase: Bound
There was a inconsistency between the storage calculation wrt `G Vs Gi`. This inconsistencies are fixed in different layers starting from gluster-block For ex: Gluster Block: https://review.gluster.org/#/c/19027/ Heketi: https://github.com/heketi/heketi/pull/935 Provisioner: https://github.com/kubernetes-incubator/external-storage/pull/496 These fixes will be part of CNS 3.9 release, I am also checking we can get these fixes in CNS 3.7. *** Bug 1537461 has been marked as a duplicate of this bug. *** This is fixed in latest gluster-block provisioner container: rhgs-gluster-block-prov-container-3.3.1-1 and cns-deploy-6.0.0-2.el7rhgs Based on comment 14 and comment 15, moving the bug to verified. 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:0642 |