Bug 973624

Summary:	[RHSC] Events log message seen when a host goes to Non-Operational needs to be changed.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shruti Sampat <ssampat>
Component:	rhsc	Assignee:	Shubhendu Tripathi <shtripat>
Status:	CLOSED ERRATA	QA Contact:	Shruti Sampat <ssampat>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	dtsang, knarra, mmahoney, pprakash, rhs-bugs, sdharane, shaines
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	bb5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:25:48 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 Shruti Sampat 2013-06-12 11:17:21 UTC

Description of problem:
---------------------------------------
When a host goes to non-operational state from the UP state, the events log message looks like this -

Gluster command [<UNKNOWN>] failed on server <UNKNOWN>.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.bb3.el6rhs 

How reproducible:
Always.

Steps to Reproduce:
1. Add a host to a cluster via the Console and let it come UP.
2. Run the following command to stop glusterd on the host - 
   # service glusterd stop

Actual results:
The following message is seen in the Events log - 

Gluster command [<UNKNOWN>] failed on server <UNKNOWN>.

Expected results:
The message should say what the command was and which server it failed in, instead of 'UNKNOWN'.

Additional info:

Comment 3 Scott Haines 2013-09-23 22:25:48 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/RHBA-2013-1262.html