Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1046055 - [RHS-C] Incorrect error message during volume create if selected bricks are created in the root partition
[RHS-C] Incorrect error message during volume create if selected bricks are c...
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
2.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Ramesh N
RHS-C QE
:
Depends On: 1046211
Blocks: 1035040
  Show dependency treegraph
 
Reported: 2013-12-23 06:48 EST by Prasanth
Modified: 2015-12-03 12:13 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
While creating volume, if the bricks are added in root partition, the error message displayed does not contain the information that 'Allow bricks in root partition and re-use the bricks by clearing xattrs' option needs to be selected to add bricks in root partition. Workaround: Select 'Allow bricks in root partition and re-use the bricks by clearing xattrs' option to add bricks in root partition.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-03 12:13:51 EST
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)
screensot of error (18.49 KB, image/png)
2013-12-23 06:48 EST, Prasanth
no flags Details

  None (edit)
Description Prasanth 2013-12-23 06:48:51 EST
Created attachment 840784 [details]
screensot of error

Description of problem:

Incorrect error message during volume create if selected bricks are created in the root partition

Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.2-0.28.beta.el6_5


How reproducible: 100%


Steps to Reproduce:
1. Click on Volumes and select "New"
2. Give a volume name and click on "Add bricks"
3. In "Brick Directory", give some brick paths in the root directory which doesn't exists. 
4. Click on OK on both the pop-up's and see the error message


Actual results: Following error message is seen in the UI:

--------
Error while executing action Create Gluster Volume: Volume create failed
error: The brick vm10_lab_eng_blr_redhat_com:/home/test is is being created in the root partition_ It is recommended that you don't use the system's root partition for storage backend_ Or use 'force' at the end of the command if you want to override this behavior_
return code: 115
---------


Expected results: Giving the same error message what gluster CLI gives doesn't make sense here. We have already introduced a Force option in the UI to allow creation of bricks in the Root partition. So the error message should be specific to UI and tell the user very clearly to select the force option available in the Add Bricks screen. i.e; to select "Allow bricks in root partition and re-use the bricks by clearing xattrs"


Additional info: screenshot of the error message attached.
Comment 1 Dusmant 2013-12-27 00:41:16 EST
Triage meeting decided that this bug fix should be deferred to the subsequent release and it should be release noted...
Comment 2 Shalaka 2014-01-30 06:36:30 EST
Please review the edited Doc Text and sign off.
Comment 3 Ramesh N 2014-02-03 23:54:12 EST
Doc text looks good.
Comment 4 Shalaka 2014-02-15 05:08:48 EST
Edited the doc text that the option to be selected is "Allow bricks in root partition and re-use the bricks by clearing xattrs" and not "force". please review and confirm.
Comment 5 Ramesh N 2014-02-18 04:05:42 EST
Doc text looks good to me.
Comment 6 Vivek Agarwal 2015-12-03 12:13:51 EST
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.

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