Bug 924748

Summary: [RHSC-SHELL] Add brick operation fails from rhsc-shell
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhsc-cliAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.1CC: dtsang, kmayilsa, knarra, mmahoney, pprakash, rhs-bugs, sdharane, shaines, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bb1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:26:09 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:
Attachments:
Description Flags
Attaching engine,vdsm and glusterfs logs none

Description RamaKasturi 2013-03-22 12:29:55 UTC 
Description of problem:

Add brick operation fails from rhsc-shell.


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


How reproducible:
Always


Steps to Reproduce:
1. Create a cluster
2. Create a volume and start it.
3. Try adding bricks to the volume using the below command.

add brick --cluster-identifier TestCluster --glustervolume-identifier vol1 --brick-brick "brick.server_id=e54b7b16-92d2-4439-9312-74f1d435bd2f,brick.brick_dir=/home/brickInfo/b15"
  
Actual results:

Add brick fails but the same action succeeds from the Console.

Expected results:

Add brick should succeed in rhsc-shell.


Additional info:
Comment 1 RamaKasturi 2013-03-22 12:48:30 UTC 
Created attachment 714523 [details]
Attaching engine,vdsm and glusterfs logs

Attaching logs.
Comment 3 Sahina Bose 2013-04-02 07:40:36 UTC 
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=923169
Comment 5 Scott Haines 2013-09-23 22:26:09 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/RHBA-2013-1262.html