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

Bug 1600812

Summary:	A new volume set option to for GD2 quota integration
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	quota	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	hari gowtham <hgowtham>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:14:36 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 hari gowtham 2018-07-13 05:47:19 UTC

Description of problem:
GD2 needs a volume set option to keep track of quota being enabled.
So we have to introduce a new volume set option in glusterfs.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
always

Steps to Reproduce:
1.create volume using GD2
2.start quota from GD2
3.

Actual results:
validation fails as no such volume option

Expected results:
validation should pass and quota should be enabled

Additional info:
this new option is needed in quota to track it being enabled.

Comment 1 Worker Ant 2018-07-13 05:53:05 UTC

REVIEW: https://review.gluster.org/20502 (quota: new volume set option to track of quota in GD2) posted (#1) for review on master by hari gowtham

Comment 2 Worker Ant 2018-07-21 03:33:25 UTC

COMMIT: https://review.gluster.org/20502 committed in master by "Amar Tumballi" <amarts> with a commit message- quota: new volume set option to track of quota in GD2

quota enable as volume set needs a new option to keep track of it.

Bugzilla ID:1600812

Change-Id: Ib8d770936bafe859f80e717409bd861760090e59
fixes: bz#1600812
Signed-off-by: Hari Gowtham <hgowtham>

Comment 3 Shyamsundar 2018-10-23 15:14:36 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/