Bug 1042777

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:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shruti Sampat <ssampat>
Component:	glusterfs	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED EOL	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	knarra, mmahoney, mmccune, sdharane, spalai, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1294033 (view as bug list)		Environment:
Last Closed:	2015-12-24 06:38:07 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:
Bug Blocks:	1042808

Description Shruti Sampat 2013-12-13 10:45:41 UTC

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.

Additional info:

Comment 2 Susant Kumar Palai 2015-12-24 06:35:59 UTC

Triage-update: Needs analysis and discussion with glusterd team.

Comment 3 Susant Kumar Palai 2015-12-24 06:38:07 UTC

This bug has reached EOL. Cloning this to 3.1.