<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:΢ÈíÑźÚ
}
--></style>
</head>
<body class='hmmessage'>
<pre style="font-family: Simsun; font-size: 12pt; ">>><i> Hi, friends, I have a problem with Pacemaker 1.1.5.
</i>>><i>
</i>>><i> When I configure a master resource as usual, and set target-role=¡°Master¡±,
</i>>><i> but all instances are in slave state, no instance is promoted to master
</i>>><i> state.
</i>>><i>
</i>>><i> Who can tell me how to promote a instance to master?
</i>
>have your RA call crm_master with a promotion preference or create a
>location constraint for the master role.
>><i>
</i>>><i> I guess it is a change in version 1.1.5, because I found ¡°+ High: PE: Bug
</i>>><i> lf#2554 - target-role alone is not sufficient to promote resources¡± in
</i>>><i> ChangeLog.
</i>
>yes
</pre><pre style="font-family: Simsun; font-size: 12pt; ">here is part of my cib.xml about the master/slave resource:</pre><pre style="font-family: Simsun; font-size: 12pt; ">...</pre><pre><font class="Apple-style-span" size="4"><master id="mastr">
<meta_attributes id="resource-mastr-meta_attributes">
<nvpair id="resource-mastr-meta_attributes-globally-unique" name="globally-unique" value="false"/>
<nvpair id="resource-mastr-meta_attributes-clone-max" name="clone-max" value="2"/>
<nvpair id="resource-mastr-meta_attributes-clone-node-max" name="clone-node-max" value="1"/>
<nvpair id="resource-mastr-meta_attributes-master-max" name="master-max" value="1"/>
<nvpair id="resource-mastr-meta_attributes-master-node-max" name="master-node-max" value="1"/>
</meta_attributes>
<primitive id="mastr-RESOURCE" class="ocf" type="master" provider="heartbeat">
<meta_attributes id="resource-mastr-RESOURCE-meta_attributes">
<nvpair id="resource-mastr-RESOURCE-meta_aa" name="priority" value="1"/>
<nvpair id="resource-mastr-RESOURCE-meta_attributes-migration-threshold" name="migration-threshold" value="0"/>
<nvpair id="resource-mastr-RESOURCE-meta_attributes-failure-timeout" name="failure-timeout" value="0"/>
<nvpair id="resource-mastr-RESOURCE-meta_attributes-is-managed" name="is-managed" value="true"/>
<nvpair id="resource-mastr-RESOURCE-meta_attributes-target-role" name="target-role" value="Master"/>
</meta_attributes>
<operations>
<op id="resource-mastr-RESOURCE-operation-start" name="start" interval="0" timeout="60s" on-fail="restart"/>
<op id="resource-mastr-RESOURCE-operation-stop" name="stop" interval="0" timeout="60s" on-fail="block"/>
<op id="resource-mastr-RESOURCE-operation-monitor" name="monitor" interval="0" timeout="60s" on-fail="restart"/>
</operations>
</primitive>
</master></font></pre><pre><font class="Apple-style-span" size="4">...</font></pre><pre><font class="Apple-style-span" size="4"><rsc_location id="constraints-rsc_location-mastr-owl0" rsc="mastr" node="owl0" score="1"/>
<rsc_location id="constraints-rsc_location-mastr-owl2" rsc="mastr" node="owl2" score="1"/></font></pre><pre><font class="Apple-style-span" size="4">...</font></pre><pre><font class="Apple-style-span" size="4"><br></font></pre><pre><font class="Apple-style-span" size="4">but when I start pacemaker, both instance on owl0 and owl1 is slave, in old pacemaker version, one of them will be promoted.</font></pre><pre><font class="Apple-style-span" size="4">I want to know how to let pacemaker promote a slave to master automatically. the version I use is the latest 1.1.5: "Pacemaker-1-1-e872eeb39a5f".</font></pre><pre><font class="Apple-style-span" size="4">thank you !!!</font></pre> </body>
</html>