Hide Forgot
Description of problem: When Master/Slave set is started, it's underlying resources have the following roles: Master: role="Master" Slaves: role="Started" When pcs resource move --master <resource> is used (which is effectively ban of master on current node), the new set looks like this: New Master: role="Master" Old Master: role="Slave" Old Slave: role="Started" Please remove this inconsistency and set them to either "Slave" or "Started" at all times. Version-Release number of selected component (if applicable): pacemaker-1.1.10-9.el6.x86_64 How reproducible: Steps to Reproduce: 1.# pcs resource create dummy ocf:pacemaker:Stateful 2.# pcs resource master dummy 3.# pcs resource move dummy-master Actual results: Inconsistent roles in pcs status xml for slave nodes Expected results: Consistent roles in pcs status xml for all slave nodes Additional info:
Tested with pcs-0.9.85-1.el6.noarch, but same results are achievable by crm_resource --resource dummy-master --move --master and crm_mon -1 -r -X
A related patch has been committed upstream: https://github.com/beekhof/pacemaker/commit/bc5e0b6 with subject: Fix: Bug rhbz#1011618 - Consistently use 'Slave' as the role for unpromoted master/slave resources Further details (if any):
Fixed in pacemaker-1.1.10-12.el6.x86_64, marking as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1635.html