Bug 1015444

Summary: [RHSC] - No event message generated when rebalance is started from CLI.
Product: Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: dpati, dtsang, mmahoney, pprakash, rhs-bugs, ssampat
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cb11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 07:50:18 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:
Attachments:
Description Flags
Message, When rebalance is started on a volume from CLI none

Description RamaKasturi 2013-10-04 09:25:36 UTC 
Description of problem:
No event message generated when rebalance is started from CLI.

Version-Release number of selected component (if applicable):
rhsc-2.1.1-0.0.2.master.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a distributed volume and start it.
2. Start rebalance on the volume from CLI using the command "gluster vol rebalance <volName> start"
3. 

Actual results:
No event message gets generated saying rebalance has started on this volume.

Expected results:
There should be an event message saying rebalance has started on this volume.


Additional info:
Comment 2 RamaKasturi 2013-12-12 12:09:59 UTC 
Verified in cb11 rhsc-2.1.2-0.27.beta.el6_5.noarch . 

Following event message gets displayed when Rebalance is started from Gluster CLi. " Detected start of rebalance on volume <volName> of Cluster <clusterName> from CLI."

Attaching the screen shot for the same.
Comment 3 RamaKasturi 2013-12-12 12:10:37 UTC 
Created attachment 835758 [details]
Message, When rebalance is started on a volume from CLI
Comment 5 errata-xmlrpc 2014-02-25 07:50:18 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/RHEA-2014-0208.html