Bug 1438325

Summary: Need to improve remove-brick failure message when the brick process is down.
Product: [Community] GlusterFS Reporter: Gaurav Yadav <gyadav>
Component: glusterdAssignee: Gaurav Yadav <gyadav>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.10CC: amukherj, bsrirama, bugs, rhs-bugs, rtalur, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.10.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1422624 Environment:
Last Closed: 2017-05-31 20:45:17 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: 1339054, 1422624    
Bug Blocks: 1423406, 1442603    

Description Gaurav Yadav 2017-04-03 05:14:52 UTC
+++ This bug was initially created as a clone of Bug #1422624 +++

+++ This bug was initially created as a clone of Bug #1339054 +++

Description of problem:
======================
If we try to remove offline brick, the operation is failing with error message "volume remove-brick start: failed: Found stopped brick <hostname>:/bricks/brick1/a1" and this condition is added newly in 3.7.9-6 build.

Currently we have use force option to remove the offline brick and same thing is expected in the failure message to use force option to remove the offline brick to guide the user.

With this users will know the how to remove the offline brick.


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-6


How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Create a simple volume of any type and start it
2. Kill one of the volume brick
3. Try to remove the killed brick (offline brick) 
4. Check the brick failure error message //message won't convey how to remove the brick.


Failure message getting:
=======================
]# gluster volume remove-brick Dis <hostname>:/bricks/brick1/a1 start
volume remove-brick start: failed: Found stopped brick <hostname>:/bricks/brick1/a1


Actual results:
================
Failure is not saying how to remove the offline brick.

Expected results:
=================
Failure message need to have force option help message to remove the offline brick.

Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-05-24 00:35:31 EDT ---

This bug is automatically being proposed for the current z-stream release of Red Hat Gluster Storage 3 by setting the release flag 'rhgs‑3.1.z' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-07-04 04:53:19 EDT ---

This bug is automatically being proposed for the current z-stream release of Red Hat Gluster Storage 3 by setting the release flag 'rhgs‑3.1.z' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

--- Additional comment from Rejy M Cyriac on 2016-09-17 12:33:32 EDT ---

Moving BZ to a transitional component in preparation for removing the 'glusterd' sub-component at the 'glusterd' component

--- Additional comment from Rejy M Cyriac on 2016-09-17 12:46:25 EDT ---

Moving BZ back to the 'glusterd' component after removal of the 'glusterd' sub-component

--- Additional comment from Worker Ant on 2017-02-16 02:47:07 EST ---

REVIEW: https://review.gluster.org/16630 (glusterd : Fix for error message while removing brick) posted (#1) for review on master by Gaurav Yadav (gyadav)

--- Additional comment from Worker Ant on 2017-02-16 03:49:53 EST ---

REVIEW: https://review.gluster.org/16630 (glusterd : Fix for error message while removing brick) posted (#2) for review on master by Gaurav Yadav (gyadav)

--- Additional comment from Worker Ant on 2017-02-17 04:56:01 EST ---

REVIEW: https://review.gluster.org/16630 (glusterd : Fix for error message while removing brick) posted (#3) for review on master by Gaurav Yadav (gyadav)

--- Additional comment from Worker Ant on 2017-02-17 04:58:55 EST ---

REVIEW: https://review.gluster.org/16630 (glusterd : Fix for error message while removing brick) posted (#4) for review on master by Gaurav Yadav (gyadav)

--- Additional comment from Worker Ant on 2017-02-17 09:47:37 EST ---

COMMIT: https://review.gluster.org/16630 committed in master by Atin Mukherjee (amukherj) 
------
commit 64637d040d7f63ef6af6588ae17a557ad0229710
Author: Gaurav Yadav <gyadav>
Date:   Thu Feb 16 13:02:20 2017 +0530

    glusterd : Fix for error message while removing brick
    
    When remove-brick command is issued to a offline brick, glusterd
    error out the operation with message -: "volume remove-brick start:
    failed: Found stopped brick <hostname>:".
    
    With this fix while removing brick, error message is modified
    to "volume remove-brick start: failed: Found stopped brick
    <brick path>. Use force option to remove the brick"
    
    Change-Id: Id40a02fc38cdb526c4629de262967fe2383febe4
    BUG: 1422624
    Signed-off-by: Gaurav Yadav <gyadav>
    Reviewed-on: https://review.gluster.org/16630
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 1 Worker Ant 2017-04-03 06:32:08 UTC
REVIEW: https://review.gluster.org/16979 (glusterd : Fix for error message while removing brick) posted (#1) for review on release-3.10 by Gaurav Yadav (gyadav)

Comment 2 Worker Ant 2017-04-13 15:32:41 UTC
COMMIT: https://review.gluster.org/16979 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit cea409d71083be2758cde0b242eba4341bd4858d
Author: Gaurav Yadav <gyadav>
Date:   Thu Feb 16 13:02:20 2017 +0530

    glusterd : Fix for error message while removing brick
    
    When remove-brick command is issued to a offline brick, glusterd
    error out the operation with message -: "volume remove-brick start:
    failed: Found stopped brick <hostname>:".
    
    With this fix while removing brick, error message is modified
    to "volume remove-brick start: failed: Found stopped brick
    <brick path>. Use force option to remove the brick"
    
    > Reviewed-on: https://review.gluster.org/16630
    > Smoke: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Atin Mukherjee <amukherj>
    
    (cherry picked from commit 64637d040d7f63ef6af6588ae17a557ad0229710)
    
    Change-Id: Id40a02fc38cdb526c4629de262967fe2383febe4
    BUG: 1438325
    Signed-off-by: Gaurav Yadav <gyadav>
    Reviewed-on: https://review.gluster.org/16979
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Samikshan Bairagya <samikshan>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Prashanth Pai <ppai>

Comment 3 Raghavendra Talur 2017-05-31 20:45: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-3.10.2, please open a new bug report.