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 1033538 - pcs does not correctly display status for cloned resource groups
Summary: pcs does not correctly display status for cloned resource groups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact:
URL:
Whiteboard:
Depends On: 1037423
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 10:42 UTC by Fabio Massimo Di Nitto
Modified: 2014-10-14 07:21 UTC (History)
5 users (show)

Fixed In Version: pcs-0.9.123-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1037423 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:21:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1526 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2014-10-14 01:22:04 UTC

Description Fabio Massimo Di Nitto 2013-11-22 10:42:27 UTC 
pcs resource create glance-fs Filesystem device="192.168.0.2:/srv/vms/clusters/nfs-storage/glance" directory="/var/lib/glance/" fstype="nfs" options="v3" --group glance

chown glance:nobody /var/lib/glance

pcs resource create glance-registry lsb:openstack-glance-registry --group glance
pcs resource create glance-api lsb:openstack-glance-api --group glance

 Resource Group: glance
     glance-fs  (ocf::heartbeat:Filesystem):    Started rhos4-node6
     glance-registry    (lsb:openstack-glance-registry):        Started rhos4-node6
     glance-api (lsb:openstack-glance-api):     Started rhos4-node6


pcs resource clone glance

pcs resource status

 Clone Set: glance-clone [glance]
     Started: [ rhos4-node5 rhos4-node6 ]

^^^^ after cloning the Resource group display is gone.
Comment 1 Andrew Beekhof 2013-11-22 20:56:08 UTC 
This is intentional by crm_mon to reduce the level of noise.
We only expand an instance of a cloned group if it is partially up/down.
Comment 2 Fabio Massimo Di Nitto 2013-11-22 21:18:14 UTC 
(In reply to Andrew Beekhof from comment #1)
> This is intentional by crm_mon to reduce the level of noise.
> We only expand an instance of a cloned group if it is partially up/down.

I am ok NOT to change the default, but can we make it optional?

pcs status --full or something?

I want to know what's running in those clones from time to time, to make sure I didn't miss bits around :)
Comment 3 Andrew Beekhof 2013-12-01 23:11:46 UTC 
IIRC, pcs is just displaying the crm_mon output here.
Chris: is that correct?

If so, we'd have to change Pacemaker.
Comment 6 Chris Feist 2013-12-02 23:48:33 UTC 
Yes, that's correct.  I can have pcs extract information from the XML that crm_mon provides, but it's easier for me just to use what crm_mon gives.

It sounds like we're going to add a new option to crm_mon, when that is ready I'll update pcs status --full to use that option.
Comment 7 Christine Caulfield 2014-02-27 10:56:48 UTC 
I've added a -R option to crm_mon that will display this. It's in upstream git.
Comment 8 Andrew Beekhof 2014-03-24 03:39:03 UTC 
We'll pick this up in the acl rebase
Comment 10 Chris Feist 2014-06-23 15:29:54 UTC 
Fix is upstream here:

https://github.com/feist/pcs/commit/8a40e89ef68a293de09352e97f89684d2f1d4d94
Comment 11 Chris Feist 2014-06-23 15:46:24 UTC 
Before Update:
[root@bid-06 pcs]# rpm -q pcs
pcs-0.9.122-3.el6.x86_64
[root@bid-06 pcs]# pcs resource create D1 Dummy --group dg
[root@bid-06 pcs]# pcs resource create D2 Dummy --group dg
[root@bid-06 pcs]# pcs resource clone dg
[root@bid-06 pcs]# pcs status --full
Cluster name: test99
Last updated: Mon Jun 23 10:42:55 2014
Last change: Mon Jun 23 10:42:49 2014 via crmd on bid-05
Stack: cman
Current DC: bid-06 - partition with quorum
Version: 1.1.11-97629de
2 Nodes configured
4 Resources configured


Online: [ bid-05 bid-06 ]

Full list of resources:

 Clone Set: dg-clone [dg]
     Started: [ bid-05 bid-06 ]

After Update:

[root@bid-06 pcs]# rpm -q pcs
pcs-0.9.123-2.el6.x86_64
[root@bid-06 pcs]# pcs status --full
Cluster name: test99
Last updated: Mon Jun 23 10:44:10 2014
Last change: Mon Jun 23 10:42:49 2014 via crmd on bid-05
Stack: cman
Current DC: bid-06 - partition with quorum
Version: 1.1.11-97629de
2 Nodes configured
4 Resources configured


Online: [ bid-05 bid-06 ]

Full list of resources:

 Clone Set: dg-clone [dg]
     Resource Group: dg:0
         D1	(ocf::heartbeat:Dummy):	Started bid-06 
         D2	(ocf::heartbeat:Dummy):	Started bid-06 
     Resource Group: dg:1
         D1	(ocf::heartbeat:Dummy):	Started bid-05 
         D2	(ocf::heartbeat:Dummy):	Started bid-05 
     Started: [ bid-05 bid-06 ]
Comment 15 errata-xmlrpc 2014-10-14 07:21:42 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.

http://rhn.redhat.com/errata/RHBA-2014-1526.html
Note You need to log in before you can comment on or make changes to this bug.