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):
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
separate resources started on different nodes
grouped resources, running on the same node
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.