1182119 – A cloned resource banned on one of the nodes is shown as Inactive in GUI

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 1182119 - A cloned resource banned on one of the nodes is shown as Inactive in GUI

Summary: A cloned resource banned on one of the nodes is shown as Inactive in GUI

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pcs
Sub Component:
Version:	7.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Ondrej Mular
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:	1189857
Blocks:
TreeView+	depends on / blocked

Reported:	2015-01-14 13:35 UTC by Radek Steiger
Modified:	2015-11-19 09:34 UTC (History)
CC List:	3 users (show)
Fixed In Version:	pcs-0.9.143-1.el7
Doc Type:	Bug Fix
Doc Text:	Cause: Cloned resource banned from running on one node is present in cluster. Consequence: In web UI cloned resource banned on one node there is false status displayed. Fix: Treat cloned resources as running when they are started on one node at least. Result: Cloned resource banned from running on one node is in web UI shown as running.
Clone Of:
Environment:
Last Closed:	2015-11-19 09:34:07 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:2290	0	normal	SHIPPED_LIVE	Moderate: pcs security, bug fix, and enhancement update	2015-11-19 09:43:53 UTC

Description Radek Steiger 2015-01-14 13:35:04 UTC

> Description of problem:

When I create a cloned resource and ban it from running on one or more of the nodes, the GUI will show it up as Inactive, whereas it is in fact running fine:

# pcs resource create dummy0 Dummy --clone
# pcs constraint location dummy0 avoids virt-044
# pcs status
...
 Clone Set: dummy0-clone [dummy0]
     Started: [ virt-041 virt-042 virt-043 ]
     Stopped: [ virt-044 ]
...

Oddly enough when I add any other resource (stopped or running, doesn't matter) the GUI will start showing the dummy0 as Running.

I believe it has the same root cause as cloning a resource with --wait flag when a ban constraint exists:

# pcs resource create dummy0 Dummy
# pcs constraint location dummy0 avoids virt-044
# pcs resource clone dummy0 --wait
Error: Unable to start clones of 'dummy0'
waiting timed out
Resource 'dummy0' is running on nodes virt-041, virt-042, virt-043.

I think in both cases it expects the clone to run on all nodes which will never materialize.


> Version-Release number of selected component (if applicable):
pcs-0.9.137-10.el7


> How reproducible:
Always

> Steps to Reproduce:
1. pcs resource create dummy0 Dummy --clone
2. pcs constraint location dummy0 avoids <node>
3. compare pcs status output and GUI state

> Actual results:
Pcs status shows the clone as stopped on one node and running on all other. GUI shows as Inactive.

> Expected results:
Both pcs status and the GUI show as running.

Comment 2 Tomas Jelinek 2015-08-10 13:18:36 UTC

Fixed in a complex rewrite of the resources page in web UI, patches in bz1189857


Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.142-2.el7.x86_64
[root@rh71-node1:~]# pcs resource create dummy0 Dummy --clone
[root@rh71-node1:~]# pcs constraint location dummy0-clone avoids rh71-node3
[root@rh71-node1:~]# pcs resource
 Clone Set: dummy0-clone [dummy0]
     Started: [ rh71-node1 rh71-node2 ]
     Stopped: [ rh71-node3 ]

The resource is shown as inactive in the web UI, yet current location is displayed correctly: rh71-node1, rh71-node2



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-1.el7.x86_64
[root@rh71-node1:~]# pcs resource create dummy0 Dummy --clone
[root@rh71-node1:~]# pcs constraint location dummy0-clone avoids rh71-node3
[root@rh71-node1:~]# pcs resource
 Clone Set: dummy0-clone [dummy0]
     Started: [ rh71-node1 rh71-node2 ]
     Stopped: [ rh71-node3 ]

The resource is shown as partially running in the web UI.

Comment 6 errata-xmlrpc 2015-11-19 09:34:07 UTC

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://rhn.redhat.com/errata/RHSA-2015-2290.html

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