Bug 1359103 - Clusters widget on main dashboard doesn't report cluster in a warning state
Summary: Clusters widget on main dashboard doesn't report cluster in a warning state
Keywords:
Status: CLOSED DUPLICATE of bug 1358506
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: UI
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2
Assignee: sankarshan
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: Console-2-GA
TreeView+ depends on / blocked
 
Reported: 2016-07-22 09:45 UTC by Martin Bukatovic
Modified: 2016-07-22 14:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-22 14:12:04 UTC
Embargoed:


Attachments (Terms of Use)
screenshot 1: cluster list page (19.32 KB, image/png)
2016-07-22 09:47 UTC, Martin Bukatovic
no flags Details
screenshot 2: clusters widget of the main dashboard (cluster status counter is missing even though there is a cluster in a warning state) (3.39 KB, image/png)
2016-07-22 09:47 UTC, Martin Bukatovic
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1356216 0 unspecified CLOSED cluster alert summary on main dashboard provides invalid data - design issues 2021-02-22 00:41:40 UTC

Internal Links: 1356216

Description Martin Bukatovic 2016-07-22 09:45:01 UTC
Description of problem
======================

When there is a cluster in a warning state (see screenshot #1), it's not
reported on Clusters widget on main dashboard (see screenshot #2).

This conflicts with the design document (USM 1.0 Overall Design), which states:

> Cluster Status (Error or Warning) - count of clusters with Error or Warning
> status, Tooltip: "N clusters need attention"

Version-Release
===============

On RHSC 2.0 server machine:

rhscon-core-selinux-0.0.28-1.el7scon.noarch
rhscon-core-0.0.28-1.el7scon.x86_64
rhscon-ui-0.0.42-1.el7scon.noarch
rhscon-ceph-0.0.27-1.el7scon.x86_64
ceph-installer-1.0.12-3.el7scon.noarch
ceph-ansible-1.0.5-23.el7scon.noarch

How reproducible
================

100 %

Steps to Reproduce
==================

1. Install RHSC 2.0 following the documentation.
2. Accept few nodes for the ceph cluster.
3. Create new ceph cluster named 'alpha'.
4. Break the cluster so that it's in a warning state (eg. HEALTH_WARN).

Actual results
==============

Check cluster state both on:

* the Clusters page, I see Warning icon there (screenshot #1).
* `ceph health` output, where I see `HEALTH_WARN`

But when I look at Clusters widget on the Main Dashboard, I don't see this
cluster reported by "Cluster Status" counter as described in the design
document. The icon and the counter is not there (see screenshot #2).

Expected results
================

When I look at Clusters widget on the Main Dashboard, I see "Cluster Status"
counter (with tooltip "1 cluster needs attention"), which links to a filtered
list of clusters in error or warning state - so just cluster alpha in this
case (since it's the only cluster in such state in this scenario).

Additional info
===============

I consider the design drafter in the design document a bit misleading, as it
suggest to use error icon for counter of clusters in either error or warning
states.

Comment 1 Martin Bukatovic 2016-07-22 09:47:01 UTC
Created attachment 1182759 [details]
screenshot 1: cluster list page

Comment 2 Martin Bukatovic 2016-07-22 09:47:49 UTC
Created attachment 1182761 [details]
screenshot 2: clusters widget of the main dashboard (cluster status counter is missing even though there is a cluster in a warning state)

Comment 3 Martin Bukatovic 2016-07-22 09:48:47 UTC
Additional info
===============

The warning icon next to the value "2" shown in Clusters widget on screenshot #2
is number of active alerts.

Comment 4 Karnan 2016-07-22 14:12:04 UTC
this is a duplicate bug.

https://bugzilla.redhat.com/show_bug.cgi?id=1358506

In above bug, fixed dashboard to show count of clusters in error, warning state.
this will be fixed as part of above bug

*** This bug has been marked as a duplicate of bug 1358506 ***


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