Bug 958813

Summary:	[RHS-C] No event messages are generated in UI when a brick goes from UP --> DOWN / DOWN --> UP
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prasanth <pprakash>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.1	CC:	dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sabose, sdharane, sharne, ssampat, tkatarki
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cb6	Doc Type:	Bug Fix
Doc Text:	Previously, users were not able to know the brick status change as the event messages were not displayed. Now, with this update, Event messages are added for brick status change.	Story Points:	---
Clone Of:	958811	Environment:
Last Closed:	2014-02-25 07:29:02 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 Prasanth 2013-05-02 12:55:00 UTC

Description of problem: 

No event messages are generated in UI when a brick goes from UP --> DOWN / DOWN --> UP


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


How reproducible: Always


Steps to Reproduce:

1. Create a "Cluster"
2. Add one or more hosts
3. Create a volume and start it
4. Find the PID of the bricks using "gluster volume status <VOLNAME>" and kill one or more bricks using # kill -9 <PID>

Once done, check the EVENTS tab for related messages. You can also check the events after bringing back the brick by restarting "glusterd"

  
Actual results: No event messages are seen in the UI, when a brick goes down and comes back.


Expected results: Event messages should be generated for these situations as it is critical for the stability of the volume.


Additional info: It's easily reproducible. However, I can attach the logs, if needed.

Comment 2 Shireesh 2013-05-13 10:37:33 UTC

Did you stop and start immediately? (within the refresh interval of 5 minutes)

Comment 3 Prasanth 2013-06-17 10:20:01 UTC

(In reply to Shireesh from comment #2)
> Did you stop and start immediately? (within the refresh interval of 5
> minutes)

No, Stop and Start was not done immediately. Event messages are NOT generated irrespective of when the operation is done.

Comment 4 Sahina Bose 2013-10-23 10:31:08 UTC

Event messages added for status change in bricks detected during the sync job. This syncing of volume status is run every 5 minutes

Comment 5 Dusmant 2013-10-25 11:47:55 UTC

*** Bug 986360 has been marked as a duplicate of this bug. ***

Comment 6 Matt Mahoney 2013-11-05 15:18:55 UTC

Verified in CB6.

Example Msg: 

Detected change in status of brick <host>:<brick> of volume T from UP to DOWN.
Detected change in status of brick <host>:<brick> of volume T from DOWN to UP.

Comment 7 Shalaka 2014-01-07 09:29:33 UTC

Please review the edited DocText and confirm.

Comment 8 Sahina Bose 2014-01-30 07:05:09 UTC

with this update, Event message - E should be lower case.
Otherwise, Doctext ok.

Comment 10 errata-xmlrpc 2014-02-25 07:29:02 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