Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 960069 - RHCS Add Brick Does Not Clear xttr's
RHCS Add Brick Does Not Clear xttr's
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity high
: ---
: RHGS 3.1.0
Assigned To: Kanagaraj
RamaKasturi
:
Depends On: 1007509 1045991
Blocks: 1202842
  Show dependency treegraph
 
Reported: 2013-05-06 10:23 EDT by Wesley Duffee-Braun
Modified: 2016-04-18 06:06 EDT (History)
17 users (show)

See Also:
Fixed In Version: rhsc-3.1.0-57
Doc Type: Bug Fix
Doc Text:
Previously, the xattrs and residual .glusterfs files were present for previously used bricks. As a consequence, the previously used bricks to create a new volume failed from Red Hat Gluster Storage Console. With this fix, force flag has been added in the option in the UI to pass "force" flag to the volume create command that clears xattrs and allows the bricks to be reused.
Story Points: ---
Clone Of:
: 1007509 (view as bug list)
Environment:
Last Closed: 2015-07-29 01:24:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Attaching screenshot for the xattrs bricks (188.03 KB, image/png)
2015-05-27 07:26 EDT, RamaKasturi
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1494 normal SHIPPED_LIVE Red Hat Gluster Storage Console 3.1 Enhancement and bug fixes 2015-07-29 05:24:02 EDT

  None (edit)
Description Wesley Duffee-Braun 2013-05-06 10:23:31 EDT
Description of problem:
When using RHSC 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.

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

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 info:
Process is done manually when using the CLI (documented here https://bugzilla.redhat.com/show_bug.cgi?id=812214), it would be useful if RHSC did the same.
Comment 2 Shireesh 2013-05-13 05:56:58 EDT
This needs a CLI
Comment 3 Wesley Duffee-Braun 2013-06-10 10:17:10 EDT
(In reply to Shireesh from comment #2)
> This needs a CLI

Hello,

Is the "This needs a CLI" in reference to the RHSC product in general or for this BZ specifically?

Thanks,
Wesley
Comment 13 Ramesh N 2015-03-26 02:05:07 EDT
Moving this to ON_QA as its already take care by the force flag in the add brick UI.
Comment 14 RamaKasturi 2015-05-22 03:29:12 EDT
Please provide the fixed in version
Comment 15 RamaKasturi 2015-05-27 07:24:06 EDT
This feature is now supported in rhsc and available for the cluster compatibility version of 3.3 and higher. 

When user tries to create a volume and click on the add brick dialog a dialog opens up and there is a check box  which says "Allow bricks in root partition and re-use the bricks by clearing xattrs" by checking this option xattrs on the bricks can be cleared.
Comment 16 RamaKasturi 2015-05-27 07:26:12 EDT
Created attachment 1030495 [details]
Attaching screenshot for the xattrs bricks
Comment 17 Divya 2015-07-26 03:33:44 EDT
Kanagaraj,

Could you review and sign-off the edited doc text.
Comment 18 Kanagaraj 2015-07-27 06:13:12 EDT
looks good.
Comment 20 errata-xmlrpc 2015-07-29 01:24:43 EDT
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/RHEA-2015-1494.html

Note You need to log in before you can comment on or make changes to this bug.