Description of problem ====================== In PGs widget on the main dashboard, a tooltip is missing for Degraded (Warning) counter of PGs. The tooltip text is specified in `USM 1.0 Overall Design` document. Version-Release =============== rhscon-ui-0.0.48-1.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 there are some PGs in warning status (eg. see steps to reproduce for BZ 1355723). 5. Go the the main dashboard and check PGs widget. Actual results ============== In the PGs widget, there is a warning icon with a number of PGs in degraded or warning state. But when you hover the mouse over it, there is no tooltip. Expected results ================ But when you hover the mouse over warning counter of PGs, the following tooltip is shown: > n PGs degraded
Created attachment 1182863 [details] screenshot 1: widgets of main dashboard
The following is the suggested text for when the user hovers over the PGs widgit: # PGs OK All Placement Groups are clean and OK. # PGs degraded There are # Placement Groups that are degraded. Ceph is currently working to resolve any inconsistencies it finds (if possible). Ceph will replay, split, scrub, repair, recover, backfill, and remap placement groups as applicable. No actions needed. # PGs error There are # Placement Groups that are in an error state that require your attention. Please refer to Red Hat Ceph Storage documentation on troubleshooting placement groups.
Tested with ceph-ansible-1.0.5-31.el7scon.noarch ceph-installer-1.0.14-1.el7scon.noarch rhscon-ceph-0.0.39-1.el7scon.x86_64 rhscon-core-0.0.39-1.el7scon.x86_64 rhscon-core-selinux-0.0.39-1.el7scon.noarch rhscon-ui-0.0.51-1.el7scon.noarch and it works.
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. https://access.redhat.com/errata/RHEA-2016:1754