[ClusterLabs] STONITH resources on wrong nodes

[Andrei Borzenkov]

11.07.2018 20:12, Salvatore D'angelo пишет:
> Does this mean that if STONITH resource p_ston_pg1 even if it runs on node pg2 if pacemaker send a signal to it pg1 is powered of and not pg2.
> Am I correct?

Yes. Resource will be used to power off whatever hosts are listed in its
pcmk_host_list. It is totally unrelated to where it is active currently.

> 
>> On 11 Jul 2018, at 19:10, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
>>
>> 11.07.2018 19:44, Salvatore D'angelo пишет:
>>> Hi all,
>>>
>>> in my cluster doing cam_mon -1ARrf I noticed my STONITH resources are not correctly located:
>>
>> Actual location of stonith resources does not really matter in up to
>> date pacemaker. It only determines where resource will be monitored;
>> resource will be used by whatever node will be selected to perform stonith.
>>
>> The only requirement is that stonith resource is not prohibited from
>> running on node by constraints.
>>
>>> p_ston_pg1	(stonith:external/ipmi):	Started pg2
>>> p_ston_pg2	(stonith:external/ipmi):	Started pg1
>>> p_ston_pg3	(stonith:external/ipmi):	Started pg1
>>>
>>> I have three node: pg1 (10.0.0.11), pg2 (10.0.0.12), and pg3 (10.0.0.13). I expected p_ston_pg3 was running on pg3, but I see it on pg1.
>>>
>>> Here my configuration:
>>> primitive p_ston_pg1 stonith:external/ipmi \\
>>> 	params hostname=pg1 pcmk_host_list=pg1 pcmk_host_check=static-list ipaddr=10.0.0.11 userid=root passwd="/etc/ngha/PG1-ipmipass" passwd_method=file interface=lan priv=OPERATOR
>>> primitive p_ston_pg2 stonith:external/ipmi \\
>>> 	params hostname=pg2 pcmk_host_list=pg2 pcmk_host_check=static-list ipaddr=10.0.0.12 userid=root passwd="/etc/ngha/PG2-ipmipass" passwd_method=file interface=lan priv=OPERATOR
>>> primitive p_ston_pg3 stonith:external/ipmi \\
>>> 	params hostname=pg3 pcmk_host_list=pg3 pcmk_host_check=static-list ipaddr=10.0.0.13 userid=root passwd="/etc/ngha/PG3-ipmipass" passwd_method=file interface=lan priv=OPERATOR
>>>
>>> location l_ston_pg1 p_ston_pg1 -inf: pg1
>>> location l_ston_pg2 p_ston_pg2 -inf: pg2
>>> location l_ston_pg3 p_ston_pg3 -inf: pg3
>>>
>>> this seems work fine on bare metal.
>>> Any suggestion what could be root cause?
>>>
>>
>> Root cause of what? Locations match your constraints.
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> https://lists.clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>