Bug 1031700

Summary:	Gluster volume set command "owner-gid" returning success for invalid argument
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Lalatendu Mohanty <lmohanty>
Component:	glusterfs	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	glusterd
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Lalatendu Mohanty 2013-11-18 15:04:57 UTC

Description of problem:

Gluster volume set command "owner-gid" returning success for wrong argument where it should return non-zero return code.

gluster volume set <volumename> owner-gid -1752
   Expected 1-255, got 0

Version-Release number of selected component (if applicable):
glusterfs-3.3.0.7rhs-1.el6rhs.x86_64.rpm


How reproducible:
always

Steps to Reproduce:
1. Create a gluster volume
2. Run "gluster volume set <volumename> owner-gid -1752" 
3. echo $?

Actual results:
Volume set command returns 0 (i.e. success)

Expected results:
it should be non zero

Additional info:

This bug is not present in RHS2.1

Comment 2 Vivek Agarwal 2015-03-23 07:40:44 UTC

The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html

Comment 3 Vivek Agarwal 2015-03-23 07:40:52 UTC

The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html