Bug 1256630
Summary: | glusterFS_native_driver: `create share`can create larger shares than requested | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | krishnaram Karthick <kramdoss> | |
Component: | openstack-manila | Assignee: | Csaba Henk <csaba> | |
Status: | CLOSED NEXTRELEASE | QA Contact: | nlevinki <nlevinki> | |
Severity: | medium | Docs Contact: | Don Domingo <ddomingo> | |
Priority: | unspecified | |||
Version: | 7.0 (Kilo) | CC: | kramdoss, scohen, sgotliv | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | 7.0 (Kilo) | Flags: | kramdoss:
needinfo-
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
The GlusterFS native driver of the File Share Service allows users to create shares of specified sizes. If no Red Hat Gluster volumes of the exact requested size exist, the driver chooses one with the nearest possible size and creates a share on the volume. Whenever this occurs, the resulting share will use the entire volume.
For example, if a user requests a 1GB share and only 2GB, 3GB, and 4GB volumes are available, the driver will choose the 2GB volume as a back end for the share. The driver will also proceed with creating a 2GB share; the user will be able to use and mount the entire 2GB share.
To work around this, implement File Share quotas for users. Doing so will prevent them from provisioning more file share storage than what they are entitled to.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1263543 (view as bug list) | Environment: | ||
Last Closed: | 2015-09-16 06:57:43 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: |
Description
krishnaram Karthick
2015-08-25 07:06:29 UTC
No fix shall be provided for upstream Kilo and thus it's not fixed in RHEL OSP7 either. It's added to the OSP7 Errata, see https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/version-7/release-notes#idm140465730614816 The bug is handled in upstream Liberty. To track the downstream port of that fix, please see the variant of this bug for OSP8: BZ #1263543 |