On 07/21/2016 08:49 AM, Ulrich Windl wrote: >>>> Ken Gaillot <[email protected]> schrieb am 19.07.2016 um 16:17 in >>>> Nachricht
> > <[email protected]>: > > > > [...] > > >> You're right -- if not told otherwise, Pacemaker will query the device>> > >> for the target list. In this case, the output of "stonith_admin -l" > > > In sles11 SP4 I see the following (surprising) output: > > "stonith_admin -l" shows the usage message > > "stonith_admin -l any" shows the configured devices, independently whether > > the given name is part of the cluster or no. Even if that host does not > > exist at all the same list is displayed: > > prm_stonith_sbd:0 > > prm_stonith_sbd > > > > Is that the way it's meant to be? > > This seems to be the behavior you get when you didn't define a > 'pcmk-host-list' and > 'dynamic-list' isn't supported either. > So the device will probably be used for fencing anything and it will be > left to the device > to fail then. > So the answer is not that wrong - might work - we just can't tell unless > you try... > > > > > >> suggests it's not returning the desired information. I'm not familiar>> > >> with the external agents, so I don't know why that would be. I > >> mistakenly assumed it worked similarly to fence_ipmilan ... Thanks everybody ! It seems to work now. For anybody interested please see the syslog messages produced further below. Yesterday we have added "pcmk_host_list=<toBeFencedNodeName>" and pcmk_host_check=static-list to the primitive resource definitions as shown below. ______________________________ New STONITH resource definitions: primitive p_ston_pg1 stonith:external/ipmi \ params hostname=pg1 pcmk_host_list=pg1 pcmk_host_check=static-list ipaddr=10.148.128.35 userid=root passwd="/var/vcap/data/packages/pacemaker/ra-tmp/stonith/PG1-ipmipass" passwd_method=file interface=lan priv=OPERATOR primitive p_ston_pg2 [...] primitive p_ston_pg3 [...] _______________________________ Syslog messages produced leading up to the fencing operation: [...] Jul 20 18:57:06 localhost pengine[5476]: warning: Node pg2 will be fenced because the node is no longer part of the cluster Jul 20 18:57:06 localhost pengine[5476]: warning: Node pg2 is unclean Jul 20 18:57:06 localhost pengine[5476]: warning: Action p_ston_pg1_stop_0 on pg2 is unrunnable (offline) Jul 20 18:57:06 localhost pengine[5476]: warning: Scheduling Node pg2 for STONITH Jul 20 18:57:06 localhost pengine[5476]: notice: Move p_ston_pg1#011(Started pg2 -> pg3) Jul 20 18:57:06 localhost pengine[5476]: warning: Calculated Transition 0: /var/lib/pacemaker/pengine/pe-warn-69.bz2 Jul 20 18:57:06 localhost crmd[5477]: notice: Executing poweroff fencing operation (49) on pg2 (timeout=60000) Jul 20 18:57:06 localhost crmd[5477]: notice: Initiating action 3: start p_ston_pg1_start_0 on pg3 Jul 20 18:57:06 localhost stonith-ng[5473]: notice: Client crmd.5477.1ea9e005 wants to fence (poweroff) 'pg2' with device '(any)' Jul 20 18:57:06 localhost stonith-ng[5473]: notice: Initiating remote operation poweroff for pg2: e669ca92-8255-4036-a57b-447de0453162 (0) Jul 20 18:57:06 localhost stonith-ng[5473]: notice: p_ston_pg3 can not fence (poweroff) pg2: static-list Jul 20 18:57:06 localhost stonith-ng[5473]: notice: p_ston_pg2 can fence (poweroff) pg2: static-list Jul 20 18:57:06 localhost stonith-ng[5473]: notice: p_ston_pg3 can not fence (poweroff) pg2: static-list Jul 20 18:57:06 localhost stonith-ng[5473]: notice: p_ston_pg2 can fence (poweroff) pg2: static-list Jul 20 18:57:07 localhost stonith-ng[5473]: notice: Operation 'poweroff' [29810] (call 2 from crmd.5477) for host 'pg2' with device 'p_ston_pg2' returned: 0 (OK) Jul 20 18:57:07 localhost stonith-ng[5473]: notice: Operation poweroff of pg2 by pg1 for [email protected]: OK Jul 20 18:57:07 localhost crmd[5477]: notice: Stonith operation 2/49:0:0:8b1582af-b779-4975-8f98-40c1ba4fa75e: OK (0) Jul 20 18:57:07 localhost crmd[5477]: notice: Peer pg2 was terminated (poweroff) by pg1 for pg1: OK (ref=e669ca92-8255-4036-a57b-447de0453162) by client crmd.5477 [...] > > > Regards, > > Ulrich > > > > _______________________________________________ > > Users mailing list: [email protected] > > http://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 > [email protected] > http://clusterlabs.org/mailman/listinfo/users > > End of Users Digest, Vol 18, Issue 42 > ************************************* _______________________________________________ Users mailing list: [email protected] http://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
