Bug 1272191 - grouped resources converted to separate resources
grouped resources converted to separate resources
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: clufter (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jan Pokorný
cluster-qe@redhat.com
:
Depends On: 1206640
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-15 13:25 EDT by Miroslav Lisik
Modified: 2017-11-07 10:54 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1206640
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
cluster.conf with service configuration (786 bytes, text/plain)
2015-10-15 13:25 EDT, Miroslav Lisik
no flags Details

  None (edit)
Description Miroslav Lisik 2015-10-15 13:25:29 EDT
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.
Comment 2 Miroslav Lisik 2017-02-02 06:19:11 EST
This bug can be closed because conversion of service element which has attribute 'exclusive="1"' is not supported.
Comment 3 Jan Pokorný 2017-05-30 12:07:33 EDT
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.
Comment 4 Jan Pokorný 2017-11-07 10:54:42 EST
Capacity asks for postponing for 7.6 consideration.

Note You need to log in before you can comment on or make changes to this bug.