Bug 978873 - [RHSC-SHELL] Add bricks gives UNKNOWN error while adding through CLI, but it gets added sucessfully for RHS U5 Nodes.
[RHSC-SHELL] Add bricks gives UNKNOWN error while adding through CLI, but it...
Status: CLOSED WONTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc-cli (Show other bugs)
2.1
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Sahina Bose
RamaKasturi
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-27 05:13 EDT by RamaKasturi
Modified: 2015-08-28 06:03 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-28 06:03:31 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 engine and vdsm logs. (7.90 MB, text/x-log)
2013-06-27 05:13 EDT, RamaKasturi
no flags Details

  None (edit)
Description RamaKasturi 2013-06-27 05:13:04 EDT
Created attachment 766019 [details]
Attaching engine and vdsm logs.

Description of problem:
Add bricks gives some error while adding through CLI, but it gets added sucessfully for RHS U5 Nodes. 

Version-Release number of selected component (if applicable):
rhsc-2.1.0-0.bb4.el6rhs.noarch
vdsm-4.9.6-24.el6rhs.x86_64
glusterfs-3.3.0.10rhs-1.el6rhs.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Create a 3.1 cluster and add u5 nodes to it.
2. Create a volume .
3. Add bricks to the volume using the following command 
add brick --cluster-identifier Testcluster --glustervolume-identifier vol1 --brick "brick.server_id=39bcf4e1-8654-498e-9c8d-b3abdcd35f2e,brick.brick_dir=/rhs/brick1/b15"

Actual results:
First time you enter the command it gives the following error but it actually adds the brick to the volume.:
unknown error: 'str' object has no attribute '_Base__context'

Expected results:
It should not give any error as described above. 

Additional info:
Comment 2 Dusmant 2015-08-28 06:03:31 EDT
We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant

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