|Summary:||grouped resources converted to separate resources|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Miroslav Lisik <mlisik>|
|Component:||clufter||Assignee:||Jan Pokorný [poki] <jpokorny>|
|Status:||NEW ---||QA Contact:||cluster-qe <cluster-qe>|
|Version:||7.2||CC:||extras-qa, jpokorny, phagara|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1206640|
Description Miroslav Lisik 2015-10-15 17:25:29 UTC
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 11:19:11 UTC
This bug can be closed because conversion of service element which has attribute 'exclusive="1"' is not supported.
Comment 3 Jan Pokorný [poki] 2017-05-30 16:07:33 UTC
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ý [poki] 2017-11-07 15:54:42 UTC
Capacity asks for postponing for 7.6 consideration.