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.

+++ This bug was initially created as a clone of Bug #1168986 +++

Description of problem:
When a clone (or master) resource with meta globally-unique=true is presented in a cluster, pcsd gui does not show any info about that cluster.  URL /managec/myCluster/status_all returns {"rh66-node2":{"bad_json":true},"rh66-node1":{"bad_json":true}}

Version-Release number of selected component (if applicable):
0.9.137

How reproducible:
always

Steps to Reproduce:
1. create a clone resource with globally-unique=true option, e.g. pcs resource create dummy Dummy --clone globally-unique=true
2. try do display nodes, resources, fence devices, acls using pcsd gui

Actual results:
No resource, fence device and acl info provided.  All nodes are displayed as offline.

Expected results:
Correct cluster information displayed in GUI.

--- Additional comment from Tomas Jelinek on 2014-12-01 06:09:46 EST ---

Test:
1. create a clone resource with globally-unique=true option, e.g. pcs resource create dummy Dummy --clone globally-unique=true
2. display nodes, resources, fence devices, acls in GUI

Created attachment 970086 [details]
proposed fix

Test:
1. create a clone resource with globally-unique=true option, e.g. pcs resource create dummy Dummy --clone globally-unique=true
2. display nodes, resources, fence devices, acls in GUI

Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.137-3.el7.x86_64
[root@rh70-node1:~]# pcs resource create dummy Dummy --clone globally-unique=true

No resource, fence device and acl information displayed in GUI.  All nodes are displayed as offline.


After Fix:
[root@rh70-node1:~]# rpm -q pcs
pcs-0.9.137-4.el7.x86_64
[root@rh70-node1:~]# pcs resource create dummy Dummy --clone globally-unique=true

Cluster information displayed in GUI.

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/RHBA-2015-0415.html