[ClusterLabs] fencing on iscsi device not working

[Andrei Borzenkov]

30.10.2019 15:46, RAM PRASAD TWISTED ILLUSIONS пишет:
> Hi everyone,
> 
> I am trying to set up a storage cluster with two nodes, both running debian
> buster. The two nodes called, duke and miles, have a LUN residing on a SAN
> box as their shared storage device between them. As you can see in the
> output of pcs status, all the demons are active and I can get the nodes
> online without any issues. However, I cannot get the fencing resources to
> start.
> 
> These two nodes were running debian jessie before and had access to the
> same LUN in a storage cluster configuration. Now, I am trying to recreate a
> similar setup with both nodes now running the latest debian. I am not sure
> if this is relevant, but this LUN already has shared VG with data on it.  I
> am wondering if this could be the cause of the trouble? Should I be
> creating my stonith device on a different/fresh LUN?
> 
> ####### pcs status
> Cluster name: jazz
> Stack: corosync
> Current DC: duke (version 2.0.1-9e909a5bdd) - partition with quorum
> Last updated: Wed Oct 30 11:58:19 2019
> Last change: Wed Oct 30 11:28:28 2019 by root via cibadmin on duke
> 
> 2 nodes configured
> 2 resources configured
> 
> Online: [ duke miles ]
> 
> Full list of resources:
> 
>  fence_duke    (stonith:fence_scsi):    Stopped
>  fence_miles    (stonith:fence_scsi):    Stopped
> 
> Failed Fencing Actions:
> * unfencing of duke failed: delegate=, client=pacemaker-controld.1703,
> origin=duke,
>     last-failed='Wed Oct 30 11:43:29 2019'
> * unfencing of miles failed: delegate=, client=pacemaker-controld.1703,
> origin=duke,
>     last-failed='Wed Oct 30 11:43:29 2019'
> 
> Daemon Status:
>   corosync: active/enabled
>   pacemaker: active/enabled
>   pcsd: active/enabled
> #######
> 
> I used the following commands to add the two fencing devices and set their
> location constraints .
> 
> #######
> sudo pcs cluster cib test_cib_cfg
> pcs -f test_cib_cfg stonith create fence_duke fence_scsi
> pcmk_host_list=duke pcmk_reboot_action="off"

According to documentation, pcmk_host_list is used only if
pcmk_host_check=static-list which is not default, by default pacemaker
queries agent for nodes it can fence and fence_scsi does not return
anything.