Bug 1611103 - online_brick_count check in volume.rc should ignore bitrot and scrubber daemons
Summary: online_brick_count check in volume.rc should ignore bitrot and scrubber daemons
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-02 04:50 UTC by Atin Mukherjee
Modified: 2018-10-23 15:16 UTC (History)
1 user (show)

Fixed In Version: glusterfs-5.0
Clone Of:
Environment:
Last Closed: 2018-10-23 15:16:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Atin Mukherjee 2018-08-02 04:50:48 UTC
Description of problem:

online_brick_count function provides the total number of bricks running for a given volume. However currently it doesn't discard the bitrot and scrubber daemons, so this function goes for a toss for a volume with bitrot enabled.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-08-02 04:52:50 UTC
REVIEW: https://review.gluster.org/20607 (tests: fix online_brick_count function) posted (#1) for review on master by Atin Mukherjee

Comment 2 Worker Ant 2018-08-03 22:46:02 UTC
COMMIT: https://review.gluster.org/20607 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- tests: fix online_brick_count function

online_brick_count should discard Bitrot and Scrubber daemon.

Change-Id: I301373ccdbeec1d1a5e6c6b137f48ed997f22556
Fixes: bz#1611103
Signed-off-by: Atin Mukherjee <amukherj>

Comment 3 Shyamsundar 2018-10-23 15:16:17 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/


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