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.
This needs a CLI
(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
Moving this to ON_QA as its already take care by the force flag in the add brick UI.
Please provide the fixed in version
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.
Created attachment 1030495 [details] Attaching screenshot for the xattrs bricks
Kanagaraj, Could you review and sign-off the edited doc text.
looks good.
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