Bug 1044598

Summary:	[RHSC] Error message on failure to start remove-brick needs correction.
Product:	Red Hat Gluster Storage	Reporter:	Shruti Sampat <ssampat>
Component:	rhsc	Assignee:	Kanagaraj <kmayilsa>
Status:	CLOSED ERRATA	QA Contact:	Shruti Sampat <ssampat>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	dpati, dtsang, kmayilsa, knarra, mmahoney, pprakash, psriniva, rhs-bugs, sabose, sankarshan, sdharane
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhsc-3.0.0-0.7.master.el6_5	Doc Type:	Bug Fix
Doc Text:	Previously when the start remove-brick operation failed, a few localization constants were displayed instead of a comprehensible error message. With this fix, the localization constants are properly mapped to appropriate messages.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-22 19:07:15 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 Shruti Sampat 2013-12-18 16:10:27 UTC

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

The error message seen on failure to start remove-brick on a volume is like this - 

Error while executing action: Cannot start remove Gluster Brick(s). One or more bricks are down.

It needs to be corrected as follows - 

Error while executing action: Cannot start removing brick(s). One or more bricks are down.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.27.beta.el6_5 

How reproducible:
Always

Steps to Reproduce:
1. On a distribute volume, kill one of the brick processes.
2. Wait till the brick status is reflected as down in the UI.
3. Select one of the bricks and click on Remove.

( The same can be tried with distributed-replicate volume with all the bricks in a replica set being killed )

Actual results:
The above described message is seen.

Expected results:
The message needs to be corrected as explained above.

Additional info:

Comment 2 Kanagaraj 2014-01-22 06:50:46 UTC

The error messages for start/stop/commit remove bricks would be 

Cannot start removing Brick(s). No up server found in C1.
Cannot stop removing Brick(s). No up server found in C1.
Cannot commit removing Brick(s). No up server found in C1.

Comment 3 Shruti Sampat 2014-06-05 09:42:02 UTC

Verified as fixed in rhsc-3.0.0-0.7.master.el6_5. 

The message seen for failure to start remove-brick is as follows when a brick of a distribute volume is down, or when all bricks of a replica set are down in a distribute-replicate volume -

Error while executing action: Cannot start removing Brick(s). One or more bricks are down.

Marking as VERIFIED.

Comment 4 Pavithra 2014-07-09 07:04:57 UTC

Hi Kanagaraj,

Please review the edited text for technical accuracy and sign off.

Comment 5 Kanagaraj 2014-07-09 09:35:20 UTC

Looks good to me.

Comment 7 errata-xmlrpc 2014-09-22 19:07:15 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-1277.html