Bug 1045991

Summary:	Add Brick Does Not Clear xttr's
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Aravinda VK <avishwan>
Component:	glusterfs	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	high	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	avishwan, chhudson, dpati, gluster-bugs, knarra, pprakash, psriniva, rnelson, sabose, vbellur, vraman, wduffee
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.53rhs	Doc Type:	Bug Fix
Doc Text:	Previously, if a brick was used by a volume, it was not possible to add that brick to any other volume even after the volume was deleted. As a result, the brick partition was rendered unusable. With this update, a "force" option is added to the 'volume create' and 'add-brick' commands.	Story Points:	---
Clone Of:	1007509	Environment:
Last Closed:	2014-02-25 08:09:58 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:	1007509
Bug Blocks:	960069

Description Aravinda VK 2013-12-23 07:02:55 UTC

+++ This bug was initially created as a clone of Bug #1007509 +++

When trying to add bricks to a volume, if the bricks had been previously used, the add can fail due to fattr's and residual /bricks/app/.glusterfs files.



How reproducible:
Always

Steps to Reproduce:
1. Select a brick that was previously used to add to a new volume
2. Attempt to add that brick
  
Actual results:
Add fails with error messages similar to below
/bricks/app or a prefix of it is already part of a volume

Expected results:
Add works correctly with the fattr's and files removed/set properly.

--- Additional comment from Anand Avati on 2013-09-25 13:43:15 EDT ---

REVIEW: http://review.gluster.org/5746 (mgmt/glusterd: Relax extended attribute checks for volume create and add brick force.) posted (#4) for review on master by Vijay Bellur (vbellur)

--- Additional comment from Anand Avati on 2013-10-17 20:16:28 EDT ---

COMMIT: http://review.gluster.org/5746 committed in master by Anand Avati (avati) 
------
commit b2a9cbe5ce61ce170a55fb3dfd7f2d6de9c52f97
Author: Vijay Bellur <vbellur>
Date:   Sat Aug 31 22:34:02 2013 +0530

    mgmt/glusterd: Relax extended attribute checks for volume create and add brick force.
    
    Expectation with force is that user is aware of the consequences of
    sanity checks not being triggered.
    
    Change-Id: I79dfeed16a23829a7217cef33ab83f9f0ffae336
    Signed-off-by: Vijay Bellur <vbellur>
    BUG: 1007509
    Reviewed-on: http://review.gluster.org/5746
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Anand Avati <avati>

Comment 3 RamaKasturi 2014-01-06 06:28:25 UTC

Verified and works fine with glusterfs-3.4.0.53rhs-1.el6rhs.x86_64.

Tested the following scenarions

1) Created a new volume with bricks which are part of another volume which was deleted.

2) Added a brick to the existing volume which was part of another volume which was deleted.

3) Removed a brick from the existing volume and added it to the new volume.

Comment 4 Pavithra 2014-01-07 09:39:30 UTC

Can you please verify the doc text for technical accuracy?

Comment 5 Aravinda VK 2014-01-07 09:55:39 UTC

Doc Text looks good to me.

Comment 7 errata-xmlrpc 2014-02-25 08:09:58 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html