Bug 1049863

Summary: [RHSC][Scale] - Brick Advanced details gives "Error in fetching brick advanced details"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED EOL QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: low    
Version: 2.1CC: asriram, mmahoney, mmccune, rhs-bugs, sabose, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When rebalance is running on multiple volumes, viewing the brick advanced details fails and the error message "could not fetch brick details, please try again later" is displayed in the Brick Advanced Details dialog box.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-03 17:12:00 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:
Bug Depends On:    
Bug Blocks: 1035040    

Description RamaKasturi 2014-01-08 11:46:25 UTC 
Description of problem:
When rebalance is started on multiple volumes and user tries to check brick advanced details it gives an "error saying could not fetch brick details. Please try again"

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.32.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create 4-8 distribute volumes.
2. Start rebalance on all the volumes at once.
3. Now click on the brick advanced details button.

Actual results:
Brick advanced details gives an error saying "could not fetch brick details, please try again later".

Expected results:
These kind of situations need to be handled properly. For example, disallow advanced brick detail when rebalance is started across multiple volumes , as the details cannot be fetched at that time.

Additional info:
Comment 2 Dusmant 2014-01-09 09:29:07 UTC 
We should document it as a known issue.
Comment 3 Shalaka 2014-01-28 11:17:32 UTC 
Please review the edited DocText and sign off.
Comment 4 Sahina Bose 2014-01-30 07:19:34 UTC 
Doctext ok
Comment 5 Vivek Agarwal 2015-12-03 17:12: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.