Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
cloned resources info does not show offline node correctly

Version-Release number of selected component (if applicable):
pacemaker-1.1.6-3.el6.x86_64

How reproducible:


Steps to Reproduce:
1. 2 of 3 nodes online
2. crm configure clone gfs2clone nfs_shared_fs
3. crm_mon
  
Actual results:
Clone Set: gfs2clone [nfs_shared_fs]
     Started: [ node01 node03 ]
     Stopped: [ nfs_shared_fs:2 ]


Expected results:
Clone Set: gfs2clone [nfs_shared_fs]
     Started: [ node01 node03 ]
     Stopped: [ node02 ]


Additional info:

This isn't how clones work I'm afraid.
No particular node own's a given instance so you can't strictly infer that nfs_shared_fs:2 was supposed to run on node2.

Also, the expected results don't scale when clone_node_max is greater than one.

thanks for clarification Andrew.