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.

Created attachment 1083315 [details]
cluster.conf with service configuration

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

Description of problem:
Resources from service groups get converted to separate resources, causing undesired behavior (resources started on different nodes).

Version-Release number of selected component (if applicable):
python-clufter-0.50.4-1.el7

How reproducible:
always

Steps to Reproduce:
1. cluster.conf with service group containing multiple resources
2. convert with clufter and deploy to pacemaker cluster
3. resources get started on different nodes

Actual results:
separate resources started on different nodes

Expected results:
grouped resources, running on the same node

Additional info:
The issue is caused by an attribute of service element which is 'exclusive="1"'. Look at the bug 1206640, comment 2.
Find attached configuration file with tested service group. If service is not set as 'exclusive' then resources are converted into one resource group, so they running on the same node.

This bug can be closed because conversion of service element which has attribute 'exclusive="1"' is not supported.

It may be per [comment 2] at the end of the day, but I'd like to dedicate
a bit of time for proper analysis, hence bumping to 7.5 at this point.

Capacity asks for postponing for 7.6 consideration.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.