Bug 1351102

Summary: Remove-brick : After remove-brick fails on a volume, the user is required to perform either commit or stop, before another task can be started
Product: [Community] GlusterFS Reporter: Sakshi <sabansal>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: annair, bugs, knarra, kramdoss, mmahoney, mmccune, nbalacha, rgowdapp, rhs-bugs, sdharane, smohan, spalai, ssampat, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: triaged, dht-remove-brick
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1294033 Environment:
Last Closed: 2017-08-29 06:22:26 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: 1294033    
Bug Blocks: 1042808    

Description Sakshi 2016-06-29 09:17:50 UTC 
+++ This bug was initially created as a clone of Bug #1294033 +++

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

Description of problem:
-------------------------

When remove-brick fails on a volume, because of brick process being killed, the user is still required to perform either commit or stop for that failed remove-brick task, before another task can be started on the volume.

After the failure of a task, the user should not be expected to perform further operations on that task before being able to start other tasks.

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

How reproducible:
Always

Steps to Reproduce:
1. Start remove-brick operation on a volume.
2. While remove-brick is in progress, kill a brick process.

Actual results:
The remove-brick task fails. But the user is expected to perform either stop or commit, before another task can be started on the volume.

Expected results:
User should not be expected to perform further operations on a failed task.
Comment 3 Nithya Balachandran 2017-08-29 06:22:26 UTC 
I have confirmed with Atin (glusterd maintainer) that this is the expected behaviour. Closing this with resolution NotABug.