On 16 Oct 2013, at 8:51 am, Andrew Beekhof <and...@beekhof.net> wrote:

> 
> On 15/10/2013, at 8:24 PM, Kazunori INOUE <kazunori.ino...@gmail.com> wrote:
> 
>> Hi,
>> 
>> I'm using pacemaker-1.1 (the latest devel).
>> I started resource (f1 and f2) which fence vm3 on vm1.
>> 
>> $ crm_mon -1
>> Last updated: Tue Oct 15 15:16:37 2013
>> Last change: Tue Oct 15 15:16:21 2013 via crmd on vm1
>> Stack: corosync
>> Current DC: vm1 (3232261517) - partition with quorum
>> Version: 1.1.11-0.284.6a5e863.git.el6-6a5e863
>> 3 Nodes configured
>> 3 Resources configured
>> 
>> Online: [ vm1 vm2 vm3 ]
>> 
>> pDummy (ocf::pacemaker:Dummy): Started vm3
>> Resource Group: gStonith3
>>    f1 (stonith:external/libvirt):     Started vm1
>>    f2 (stonith:external/ssh): Started vm1
>> 
>> 
>> "reset" of f1 which hasn't been started on vm2 was performed when vm3 is 
>> fenced.
>> 
>> $ ssh vm3 'rm -f /var/run/Dummy-pDummy.state'
>> $ for i in vm1 vm2; do ssh $i 'hostname; egrep " reset | off "
>> /var/log/ha-log'; done
>> vm1
>> Oct 15 15:17:35 vm1 stonith-ng[14870]:  warning: log_operation:
>> f2:15076 [ Performing: stonith -t external/ssh -T reset vm3 ]
>> Oct 15 15:18:06 vm1 stonith-ng[14870]:  warning: log_operation:
>> f2:15464 [ Performing: stonith -t external/ssh -T reset vm3 ]
>> vm2
>> Oct 15 15:17:16 vm2 stonith-ng[9160]:  warning: log_operation: f1:9273
>> [ Performing: stonith -t external/libvirt -T reset vm3 ]
>> Oct 15 15:17:46 vm2 stonith-ng[9160]:  warning: log_operation: f1:9588
>> [ Performing: stonith -t external/libvirt -T reset vm3 ]
>> 
>> Is it specifications?
> 
> Yes, although the host on which the device is started usually gets priority.
> I will try to find some time to look through the report to see why this 
> didn't happen.

Reading through this again, it sounds like it should be fixed by your earlier 
pull request:

   https://github.com/beekhof/pacemaker/commit/6b4bfd6

Yes?

> I'm kind of swamped at the moment though.
> 
>> 
>> Best Regards,
>> Kazunori INOUE
>> <stopped_resource_performed_reset.tar.bz2>_______________________________________________
>> 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://bugs.clusterlabs.org

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
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://bugs.clusterlabs.org

Reply via email to