Bug 1044009 - MaxAlloc and AllocCount differs from gluster cli when running `list bricks --cluster-identifier <cluserid> --glustervolume-identifier <glusterid> --show-all --all_content True`
Summary: MaxAlloc and AllocCount differs from gluster cli when running `list bricks -...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc-cli
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 15:31 UTC by Dustin Tsang
Modified: 2016-10-27 08:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 08:08:49 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dustin Tsang 2013-12-17 15:31:46 UTC
Description of problem:

MaxAlloc and AllocCount differs from gluster cli when running `list bricks  --cluster-identifier <cluserid> --glustervolume-identifier <volume id> --show-all --all_content True`


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

How reproducible:
every time


Steps to Reproduce:
1. create dist volume
2. start the volume 
3. run MaxAlloc and AllocCount differs from gluster cli when running `list bricks  --cluster-identifier <cluserid> --glustervolume-identifier <volume id> --show-all --all_content True`
4. run gluster volume stats <volume name> mem
5. compare all memory statistics for the first brick from the results in steps 3 and 4

Actual results:

MaxAlloc and AllocCount always differ every time the steps above are run


Expected results:
MaxAlloc and AllocCount should match


Additional info:

Comment 2 Sahina Bose 2013-12-17 16:13:44 UTC
Possibly not a bug, as memory count will vary for each run unless there's a significant difference between API and gluster CLI

Comment 6 Sahina Bose 2016-10-27 08:08:49 UTC
Closing this bug as rhsc sdk/cli are not supported.


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