Bug 1048096 - [RHSC] gluster CLI usage information shown in the volume creation error message
Summary: [RHSC] gluster CLI usage information shown in the volume creation error message
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Dusmant
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-03 07:24 UTC by Shruti Sampat
Modified: 2016-02-18 00:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:13:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Shruti Sampat 2014-01-03 07:24:56 UTC
Description of problem:
-------------------------

When trying to create a volume with the name volume, the following error message is seen on the UI - 

Error while executing action Create Gluster Volume: Command execution failed
error: "volume" cannot be the name of a volume_
Usage: volume create [stripe ] [replica ] [device vg] [transport ] ___ [force]
return code: 1

The usage information and return code is only relevant to a user of the gluster CLI and not to a user of the RHSC. That needs to be removed.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.32.el6rhs 

How reproducible:
Always

Steps to Reproduce:
1. Try to create a volume named 'volume'.

Actual results:
The above described error message is seen.

Expected results:
Remove usage information and return code.

Additional info:

Comment 2 Vivek Agarwal 2015-12-03 17:13:00 UTC
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.