Bug 844333 - FutureFeature: Alert propogation should change status indicators for cluster, nodes and volumes
Summary: FutureFeature: Alert propogation should change status indicators for cluster,...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
: 843817 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 10:33 UTC by Paul Cuzner
Modified: 2018-01-29 15:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-29 15:14:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Paul Cuzner 2012-07-30 10:33:58 UTC
Description of problem:
Current status information is binary - on or off (green or red arrow symbols). However, given the potential scale of a cluster and the components involved, component failures within the cluster should introduce a warning state to the objects in RHS-C. See below

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
Some examples of where have a 3rd state for objects would prove beneficial;

if replication status goes faulty - volume should go yellow, and this yellow status propogate to the cluster object in the GUI
If a server goes down - it should show red (which it currently does), but the cluster should show yellow indicating a component within the cluster has a problem
if a drive fails on a node, the host and volume states that rely on the raid group holding the failed drive should be updated.


Additional info:

Comment 2 Shireesh 2012-08-14 10:01:19 UTC
Definitely a very useful requirement. We'll try to incorporate this soon.

Comment 3 Shireesh 2012-11-16 08:52:38 UTC
*** Bug 843817 has been marked as a duplicate of this bug. ***

Comment 8 Sahina Bose 2018-01-29 15:14:15 UTC
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken


Note You need to log in before you can comment on or make changes to this bug.