Bug 1236503

Summary:	Disabling enable-shared-storage deletes the volume with the name - "gluster_shared_storage"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	glusterd	Assignee:	Gaurav Kumar Garg <ggarg>
Status:	CLOSED ERRATA	QA Contact:	Byreddy <bsrirama>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, asengupt, bmohanra, bsrirama, byarlaga, ggarg, mlawrenc, nlevinki, rhs-bugs, rjoseph, sankarshan, smohan, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.2
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.5-0.3	Doc Type:	Bug Fix
Doc Text:	Previously, disabling enable-shared-storage deleted the volume with the name "gluster_shared_storage". With this fix, disabling cluster.enable-shared-storage does not delete of any volume named 'gluster_shared_storage'.	Story Points:	---
Clone Of:
Clones:	1266818 1319695 (view as bug list)		Environment:	RHEL 6.7
Last Closed:	2016-03-01 05:27:02 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:	1216951, 1260783, 1266818

Description SATHEESARAN 2015-06-29 09:18:31 UTC

Description of problem:
-----------------------
Consider the case where the shared storage volume - which will be used for snapshot-scheduler, NFS Ganesha, geo-replication - was manually created.
Disabling enable-shared-storage actually deletes this volume, though it was not created by enabling enable-shared-storage

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1 Nightly build ( glusterfs-3.7.1-6.el6rhs )

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a volume of any type with the name - "gluster_shared_storage"
2. Disable shared storage by enabling enable-shared-storage
   # gluster volume set all cluster.enable-shared-storage disable

Actual results:
---------------
"gluster_shared_storage" volume which was created manually gets deleted

Expected results:
-----------------
"gluster_shared_storage" volume should not get deleted, as the volume was not created by enabling gluster-shared-storage

Additional info:
-----------------
[root@ ~]# gluster volume create gluster_shared_storage
10.70.37.46:/tmp/1 force
volume create: gluster_shared_storage: success: please start the
volume to access data

[root@ ~]# gluster volume set all cluster.enable-shared-storage enable
volume set: failed: Shared storage volume(gluster_shared_storage)
already exists.

[root@ ~]# gluster volume set all cluster.enable-shared-storage disable
Disabling cluster.enable-shared-storage will delete the shared storage
volume(gluster_shared_storage), which is used by snapshot scheduler,
geo-replication and NFS-Ganesha. Do you still want to continue? (y/n) y
volume set: success

[root@ ~]# gluster volume status gluster_shared_storage
Volume gluster_shared_storage does not exist

Comment 2 senaik 2015-07-03 06:58:11 UTC

Avra, 

Could you please provide the doc text for this bug?

Comment 3 monti lawrence 2015-07-22 19:30:09 UTC

Doc text is edited. Please sign off to be included in Known Issues.

Comment 4 SATHEESARAN 2015-07-23 08:50:55 UTC

Setting needinfo on Avra as he has given the doc_text for known_issue

Comment 5 Gaurav Kumar Garg 2015-07-27 05:36:09 UTC

hi,

this doc text looks good to me.

Comment 6 Anand Nekkunti 2015-10-05 05:47:32 UTC

Upstream patch :http://review.gluster.org/#/c/12232/

Comment 9 Byreddy 2015-10-21 06:29:18 UTC

Verified Steps:
===============
1. Create a volume of type  Distributed with the name - "gluster_shared_storage"
2. Disabled shared storage by enable-shared-storage disable"
   # gluster volume set all cluster.enable-shared-storage disable
3. Volume created in step-1 was not delete by  enable-shared-storage disable.

RHGS ver: glusterfs-3.7.5-0.3

Fix is working good.

Comment 11 errata-xmlrpc 2016-03-01 05:27:02 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://rhn.redhat.com/errata/RHBA-2016-0193.html