RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1264950 - Logic issues with displaying of status of resource group in web UI dashboard.
Summary: Logic issues with displaying of status of resource group in web UI dashboard.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-21 17:28 UTC by Miroslav Lisik
Modified: 2015-11-13 14:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-13 14:07:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miroslav Lisik 2015-09-21 17:28:22 UTC
Description of problem:

When you have a resource group with more than one resource and the resources have issues, then color of group status is not set according to the issue with highest priority on the dashboard in pcs web UI.

Version-Release number of selected component (if applicable):
pcs-0.9.143-9.el7.x86_64

How reproducible:
always

Steps to Reproduce:

1. Setup resource group.

[root@virt-028 ~]# pcs resource create before Dummy --group apache-group
[root@virt-028 ~]# pcs resource create apache apache --group apache-group
[root@virt-028 ~]# pcs resource 
 Resource Group: apache-group
	 before	(ocf::heartbeat:Dummy):	Started virt-028
	 apache	(ocf::hea.rtbeat:apache):	Started virt-028

2. Cause apache failure.

Move apache configuration file on all cluster nodes.
[root@virt-028 ~]# mv /etc/httpd/conf/httpd.conf ~/httpd.conf

The apache-group has status of "partially running" with red color and "Failed" icon and cluster has "Warning" icon
and it is counted as warning on the top row.

3. Cause a failed action on the 'before' resource.
[root@virt-028 ~]# crm_resource --resource before --fail -H virt-028

Color of status changed from red to orange. Cluster is counted under "Warning" icon.

Actual results:
The color of status of resource group is not set according to resource with higher priority issue.
(e.g. in resource group is a running resource with one failed monitor action and stopped apache resource with failed action - resource group status is "partially running" with orange color)

Expected results:
When you have more resources in a resource group, then status of resource group has color according to resource with higher priority issue.

Comment 1 Miroslav Lisik 2015-11-13 14:07:32 UTC
I am not able to reproduce this anymore with pcs-0.9.143-15.el7.


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