Bug 975766

Summary:	[RHS-C] Event message doesn't mention the type of conflict detected
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prasanth <pprakash>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED WONTFIX	QA Contact:	RHS-C QE <rhsc-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.1	CC:	dpati, knarra, mmahoney, mmccune, rhs-bugs, sdharane, ssampat
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-28 10:00: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 Prasanth 2013-06-19 10:08:34 UTC

Description of problem:

Event message doesn't mention the type of conflict detected.

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. Create Content conflict and see the events
2. Create Status conflict and see the events
3. Create Missing conflict and see the events

Actual results: Following is the event message generated for all 3 types of conflicts:

"Detected conflict in hook <HOOK_NAME> of Cluster <CLUSTER_NAME>


Expected results: The event message should clearly indicate the type of conflict (Status Conflict/Content Conflict/Missing Conflict) it detected.


Additional info:

Comment 2 Sahina Bose 2013-07-31 11:58:47 UTC

We will keep the event messages as is, but will provide the list of conflicts on hover over the exclamation mark on hooks tab.

Comment 5 Dusmant 2015-08-28 10:00:48 UTC

We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant