<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>>> Hi all,<br><div><pre>>> while creating a cloned stonith resource<br>> <br>> Any particular reason you feel the need to clone it?<br> <br>In the end, I suppose it's only a "purist mindset" :) because it is a PDU whose power outlets control both nodes, so<br>its resource "should be" active (and monitored) on both nodes "independently".<br>I understand that it would work anyway, leaving it not cloned and not location-constrained<br>just as regular, "dedicated" stonith devices would not need to be location-constrained, right?<br><br>>> for multi-level STONITH on a fully-up-to-date CentOS 6.5 (pacemaker-1.1.10-14.el6_5.3.x86_64):<br>>> <br>>> pcs cluster cib stonith_cfg<br>>> pcs -f stonith_cfg stonith create pdu1 fence_apc action="off" \<br>>> ipaddr="pdu1.verolengo.privatelan" login="cluster" passwd="test" \ pcmk_host_map="cluster1.verolengo.privatelan:3,cluster1.verolengo.privatelan:4,cluster2.verolengo.privatelan:6,cluster2.verolengo.privatelan:7" \<br>>> pcmk_host_check="static-list" pcmk_host_list="cluster1.verolengo.privatelan,cluster2.verolengo.privatelan" op monitor interval="240s"<br>>> pcs -f stonith_cfg resource clone pdu1 pdu1Clone<br>>> pcs -f stonith_cfg stonith level add 2 cluster1.verolengo.privatelan pdu1Clone<br>>> pcs -f stonith_cfg stonith level add 2 cluster2.verolengo.privatelan pdu1Clone<br>>> <br>>> <br>>> the last 2 lines do not succeed unless I add the option "--force" and even so I still get errors when issuing verify:<br>>> <br>>> [root@cluster1 ~]# pcs stonith level verify<br>>> Error: pdu1Clone is not a stonith id<br>> <br>> If you check, I think you'll find there is no such resource as 'pdu1Clone'.<br>> I don't believe pcs lets you decide what the clone name is.<br><br>You're right! (obviously ;> )<br>It's been automatically named pdu1-clone<br><br>I suppose that there's still too much crmsh in my memory :)<br><br>Anyway, removing the stonith level (to start from scratch) and using the correct clone name does not change the result:<br><br>[root@cluster1 etc]# pcs -f stonith_cfg stonith level add 2 cluster1.verolengo.privatelan pdu1-clone<br>Error: pdu1-clone is not a stonith id (use --force to override)<br>[root@cluster1 etc]# pcs -f stonith_cfg stonith level add 2 cluster1.verolengo.privatelan pdu1-clone --force<br>[root@cluster1 etc]# pcs -f stonith_cfg stonith level verify<br>Error: pdu1-clone is not a stonith id<br>[root@cluster1 etc]# echo $?<br>1<br><br>I suppose that I should devise a testing strategy (like pulling iLO cables and causing a stonith to happen) to verify it.<br> <br>Many thanks again for your help.<br><br>Regards,<br>Giuseppe<br><br><br></pre></div> </div></body>
</html>