Bug 1024227

Summary:	[RHS-C] Stop remove brick does not show the remove brick status
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ramesh N <rnachimu>
Component:	rhsc	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	2.1	CC:	dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sdharane, ssampat
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	Cb6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-25 07:57:01 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:

Description Ramesh N 2013-10-29 07:31:26 UTC

Description of problem:

  When user tries to stop remove brick, remove brick status is not shown by default. 

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


How reproducible:
Always

Steps to Reproduce:
1. Create a volume with bricks
2. Start removing the bricks (with migration)
3. Stop the removal operation before migration completes

Actual results:

  Status of the data migration is not shown

Expected results:

  After stopping the removal operation, data  migration status should be shown to the user.

Additional info:

 This is similar to stop rebalance use case

Comment 2 Prasanth 2013-11-13 08:21:08 UTC

Verified in cb6.

Remove brick status is now shown by default after executing Stop remove brick.

Comment 3 Ramesh N 2014-01-03 11:44:17 UTC

Doc Text is not required  as its a new feature and we already have an RFE

Comment 5 errata-xmlrpc 2014-02-25 07:57:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0208.html