[Pacemaker] bug: target-role=master ignores master-max setting in m/s resource

[Rasto Levrinc]

With the following config the dummy resource is promoted on both nodes to
master, although master-max="1". XML is attached.

node $id="8165b1f7-da29-43db-8510-065ac1d33469" sles11-b
node $id="bb56fda4-7d0d-405c-a6e4-c21b0e070303" sles11-a
primitive res_Stateful_1 ocf:pacemaker:Stateful
ms ms_res_Stateful_1 res_Stateful_1 \
        meta clone-max="2" master-max="1" target-role="master"
property $id="cib-bootstrap-options" \
        dc-version="1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7" \
        cluster-infrastructure="Heartbeat"

Rasto

-- 
: Dipl-Ing Rastislav Levrinc
: DRBD-MC http://www.drbd.org/mc/management-console/
: DRBD/HA support and consulting http://www.linbit.com/
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cib-master.xml
Type: text/xml
Size: 4509 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091015/d4a37abf/attachment-0003.xml>