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:
dlm-clone resources do not start on all nodes in 16-node cluster.
In fact it only starts on two nodes, while the rest is showing the resource as stopped.

There are no error traces, failcounts on zero, enable/disable does not change anything.

Version-Release number of selected component (if applicable):
pacemaker-1.1.10-27.el7.x86_64

How reproducible:
always?

Steps to Reproduce:
1. setup dlm-cloned resources on 16-node cluster (standard QA setup test on 16 nodes)
2.
3.

Actual results:
only two nodes will have dlm-clone resource started (and the test fails)

Expected results:
all nodes have dlm-clone resource running

Additional info:

it seems to affect 11 and more node clusters, reducing the cluster to 10 live nodes resulted in expected setup (offlining the nodes via pcs cluster stop is enough).

(In reply to Jaroslav Kortus from comment #2)
> it seems to affect 11 and more node clusters, reducing the cluster to 10
> live nodes resulted in expected setup (offlining the nodes via pcs cluster
> stop is enough).

good catch, it is related to having over 10 cloned instances.

I've created a patch upstream.

https://github.com/ClusterLabs/pacemaker/pull/465

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.