Bug 1044489

Summary:	After stopping remove brick from gluster cli, commit and retain is still allowed from UI .
Product:	Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	rhsc	Assignee:	Dusmant <dpati>
Status:	CLOSED WONTFIX	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.1	CC:	mmahoney, mmccune, rhs-bugs, sabose, sankarshan, shtripat, ssampat
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-01 13:53:44 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:

Description RamaKasturi 2013-12-18 12:35:24 UTC

Description of problem:
After stopping remove brick from gluster cli, question mark icon appeared in the ui , but after a few seconds it changed to data migration and pending commit icon and clicking on commit removes the brick.

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.28.beta.el6_5.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a distribute volume and start it.
2. Now start remove brick, wait till the  data migration is completed.
3. stop remove brick from CLI by using the command "gluster vol remove-brick <volName> <brickPath> stop"

Actual results:
1) '?' mark icon appeared in the UI.
2) After a few seconds, icon changed to remove-brick icon with pending commit.
3) Commiting the brick was sucessful.

Expected results:
1) Icon should remain as question mark, only status should be enabled.



Additional info:

Comment 1 RamaKasturi 2013-12-18 12:40:15 UTC

Please find the sos reports here

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1044489

Comment 4 Shubhendu Tripathi 2013-12-19 06:11:49 UTC

This seems to be an issue with GLUSTER.

Tried the below commands from gluster CLI and it allows the commit even after stop is executed after remove brick.

1. 'gluster volume remove-brick <volname> <bricks> start' to start the remove brick operation. Waited for the completion of the same.
2. 'gluster volume remove-brick <volname> <bricks> status' shows the status as completed
3. 'gluster volume remove-brick <volname> <bricks> stop' stops the operation
4. 'gluster volume remove-brick <volname> <bricks> status' shows the status as completed
5. 'gluster volume remove-brick <volname> <bricks> commit' allowed and removes the brick permanently

In Console, the status changes to COMPLETED with action pending because the command 'gluster volume remove-brick <volname> <bricks> status' returns a status as COMPLETED. And as the status is completed in UI commit & retain is enabled and it allows the action. Ideally in such a case GLUSTER should fail for commit if stop is already executed from CLI after completion of remove-brick.

Comment 5 Dusmant 2015-09-01 13:53:44 UTC

We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant