Hi Andrew, I registered this problem on Bugzilla.
* http://developerbugs.linux-foundation.org/show_bug.cgi?id=2476 Best Regards, Hideo Yamauchi. --- renayama19661...@ybb.ne.jp wrote: > Hi, > > I compared movement in a version of pacemaker about this problem. > > * 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b > > [r...@srv02 ~]# crm_mon -1 > ============ > Last updated: Fri Aug 13 13:02:24 2010 > Stack: openais > Current DC: srv01 - partition with quorum > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b > 2 Nodes configured, 2 expected votes > 1 Resources configured. > ============ > > Online: [ srv01 srv02 ] > > Resource Group: UMgroup01 > UmVIPcheck (ocf::heartbeat:Dummy): Started srv02 > UmIPaddr (ocf::heartbeat:Dummy2): Started srv01 (unmanaged) > FAILED > > Failed actions: > UmIPaddr_stop_0 (node=srv01, call=9, rc=1, status=complete): unknown error > > * 1.0.8-94bf2cc9219b11310f7d3e310f3623bf85e20bf9 > > [r...@srv01 ~]# crm_mon -1 > ============ > Last updated: Fri Aug 13 12:47:08 2010 > Stack: openais > Current DC: srv01 - partition with quorum > Version: 1.0.8-94bf2cc9219b11310f7d3e310f3623bf85e20bf9 > 2 Nodes configured, 2 expected votes > 1 Resources configured. > ============ > > Online: [ srv01 srv02 ] > > Resource Group: UMgroup01 > UmVIPcheck (ocf::heartbeat:Dummy): Started srv01 > UmIPaddr (ocf::heartbeat:Dummy2): Started srv01 (unmanaged) > FAILED > > Failed actions: > UmIPaddr_stop_0 (node=srv01, call=7, rc=1, status=complete): unknown error > > > In the old version, on-fail=block seems to work definitely somehow or other. > > The next change influences the difference of the movement. > > * http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/6bf91e9195fe > > Is this revision right? > > I do not understand contents of the bugs(lf#1959) well, but wish > on-fail=block works in the same > way > as the past. > > Best Regards, > Hideo Yamauchi. > > > > --- renayama19661...@ybb.ne.jp wrote: > > > Hi, > > > > Let me confirm it about specifications of on-fail="block". > > > > > > I constituted the following cluster. > > > > ============ > > Last updated: Mon Aug 9 11:18:29 2010 > > Stack: openais > > Current DC: srv01 - partition with quorum > > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b > > 2 Nodes configured, 2 expected votes > > 1 Resources configured. > > ============ > > > > Online: [ srv01 srv02 ] > > > > Resource Group: UMgroup01 > > UmVIPcheck (ocf::heartbeat:Dummy): Started srv01 > > UmIPaddr (ocf::heartbeat:Dummy2): Started srv01 > > > > > > The error of the UmIPaddr resource of this time set it in block.。 > > > > <group id="UMgroup01"> > > <primitive class="ocf" type="Dummy" provider="heartbeat" > > id="UmVIPcheck"> > > <operations> > > <op id="op-umVIPcheck-start" interval="0" name="start" > > timeout="90s" > > on-fail="restart" > > start-delay="2s"/> > > </operations> > > </primitive> > > <primitive class="ocf" type="Dummy2" provider="heartbeat" > > id="UmIPaddr"> > > <operations> > > <op id="op-umIPaddr-start" interval="0" name="start" > > timeout="60s" > > on-fail="restart"/> > > <op id="op-umIPaddr-monitor" interval="10" name="monitor" > > timeout="60s" > > on-fail="restart"/> > > <op id="op-umIPaddr-stop" interval="0" name="stop" > > timeout="60s" on-fail="block"/> > > </operations> > > </primitive> > > </group> > > > > > > UmVIPcheck moves to a srv02 node when I generate a stop error in UmIPaddr > > artificially then. > > UmIPaddr does not move. > > > > > > ============ > > Last updated: Mon Aug 9 11:19:19 2010 > > Stack: openais > > Current DC: srv01 - partition with quorum > > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b > > 2 Nodes configured, 2 expected votes > > 1 Resources configured. > > ============ > > > > Online: [ srv01 srv02 ] > > > > Resource Group: UMgroup01 > > UmVIPcheck (ocf::heartbeat:Dummy): Started srv02 > > UmIPaddr (ocf::heartbeat:Dummy2): Started srv01 (unmanaged) > > FAILED > > > > Failed actions: > > UmIPaddr_stop_0 (node=srv01, call=8, rc=1, status=complete): unknown > > error > > > > > > Setting of UmIPaddr acted and thought that UmVIPcheck did not > > move.(on-fail="block") > > > > I have forgotten whether this movement was specifications. > > > > Is this movement specifications? > > Was there the setting that did not move other group resources?(not move > > UmVIPcheck) > > > > > > Best Regards, > > Hideo Yamauchi. > > > > > > > _______________________________________________ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: > > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker