Bug 1370991 - Event: Health of cluster 'ceph' degraded from HEALTH_OK to HEALTH_WARN but Reason of HEALTH_WARN is not covered
Summary: Event: Health of cluster 'ceph' degraded from HEALTH_OK to HEALTH_WARN but Re...
Keywords:
Status: CLOSED DUPLICATE of bug 1352108
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: Ceph
Version: 2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 2
Assignee: Shubhendu Tripathi
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 06:11 UTC by Vikhyat Umrao
Modified: 2016-09-01 13:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-01 13:28:07 UTC
Target Upstream Version:


Attachments (Terms of Use)
Event Health_OK to Health_WARN (15.27 KB, image/png)
2016-08-29 06:13 UTC, Vikhyat Umrao
no flags Details
Cluster Health Changed (41.25 KB, image/png)
2016-08-29 06:14 UTC, Vikhyat Umrao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1352108 0 unspecified CLOSED Details of a cluster state (what went wrong and why) is not available anywhere in the RHSC 2.0 ui 2021-02-22 00:41:40 UTC

Internal Links: 1352108

Description Vikhyat Umrao 2016-08-29 06:11:44 UTC
Description of problem:

Event: Health of cluster 'ceph' degraded from HEALTH_OK to HEALTH_WARN but Reason of HEALTH_WARN is not covered 

We should tell the reason why  cluster is degraded from HEALTH_OK to HEALTH_WARN.
Earlier in calamari this feature was available.


Version-Release number of selected component (if applicable):
Red Hat Storage Console 2

How reproducible:
Always


PFA, screenshots in next comments.

Comment 1 Vikhyat Umrao 2016-08-29 06:13:20 UTC
Created attachment 1195167 [details]
Event Health_OK to Health_WARN

Comment 2 Vikhyat Umrao 2016-08-29 06:14:10 UTC
Created attachment 1195168 [details]
Cluster Health Changed

Comment 3 Martin Bukatovic 2016-09-01 13:12:10 UTC
Could you review BZ 1352108 and check if this BZ is a duplicate?

Comment 4 Vikhyat Umrao 2016-09-01 13:28:07 UTC
(In reply to Martin Bukatovic from comment #3)
> Could you review BZ 1352108 and check if this BZ is a duplicate?

Thank you Martin yes it is a duplicate. Marking it.

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


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