Bug 1238332

Summary:	unending remove brick undetermined state
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Lubos Trilety <ltrilety>
Component:	rhsc	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED CANTFIX	QA Contact:	RHS-C QE <rhsc-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	anbabu, asriram, ltrilety, mlawrenc, nlevinki, rhs-bugs, sabose, sankarshan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	When the console doesn't know that glusterd is not running on the host, removal of a brick results in an undetermined state (question mark). When glusterd is started again, the brick remains in an undetermined state. The volume command shows status as "not started" but the remove-brick status command returns null in the status field. Workaround: Stop/commit remove-brick from the CLI.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-13 06:25:22 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:	1216951

Description Lubos Trilety 2015-07-01 15:39:03 UTC

Description of problem:
When glusterd service isn't running on the host, however console doesn't find out that yet. Remove of the brick placed on such host could be invoked from the console, it ends with undetermined state, question-mark icon. However when glusterd is started again on the host it doesn't change back to remove brick icon and remains in undetermined state.
No other task can be run from GUI the task is not finished, however it cannot be stopped from GUI, only 'Status' button is enabled.


Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.61

How reproducible:
100%

Steps to Reproduce:
1. Stop glusterd on rhgs server
2. Invoke remove brick, which is located on the machine with stopped glusterd service, using GUI
(The confirm dialog could be prepared before the glusterd is stopped on the machine)
3. State goes to undetermined with question-mark icon
4. Start glusterd service on the machine
5. Look on the state of the task


Actual results:
GUI:
'Remove brick status could not be determined'
and 'Remove Brick Status' window is empty
CLI:
# gluster volume status <volname>
....
Status               : not started

Expected results:
Remove brick should be cancelled or it should continue correctly

Additional info:

Comment 1 Sahina Bose 2015-07-02 09:54:23 UTC

This seems like a corner case, why is the severity high?

Comment 2 Lubos Trilety 2015-07-02 11:25:02 UTC

(In reply to Sahina Bose from comment #1)
> This seems like a corner case, why is the severity high?

Because it blocks work with the volume from GUI. However you're right it's kind of a corner case, changed to medium.

Comment 3 monti lawrence 2015-07-22 19:43:28 UTC

Doc text is edited. Please sign off to be included in Known Issues.

Comment 4 anmol babu 2015-07-23 11:19:03 UTC

Edited doc-text. Edited text looks good to me

Comment 6 Sahina Bose 2016-04-13 06:25:22 UTC

A workaround has been suggested for this bug. Once glusterd is stopped on the server, console cannot perform actions on server - so closing this as we do not currently have a way to fix this scenario