[ClusterLabs] Setup problem: couldn't find command: tcm_node

[Jason A Ramsey]

Thanks for the response, but as I indicated in a previous response, lio-utils is deprecated, having been replaced by targetcli. It seems as though Pacemaker is trying to invoke a set of utilities/libraries that aren’t currently supported to perform iSCSI Target/LUN clustering. My question becomes, therefore, how does one retarget Pacemaker at the right/current toolset?

--
 
[ jR ]
  M: +1 (703) 628-2621
  @: jason at eramsey.org
 
  there is no path to greatness; greatness is the path

On 7/20/16, 10:55 PM, "Zhu Lingshan" <lszhu at suse.com> wrote:

    Hi Jason,
    
    tcm_node is in a package called lio-utils. If it is SUSE, you can try to 
    zypper in lio-utils.
    
    
    Thanks,
    BR
    Zhu Lingsan
    
    On 07/20/2016 11:08 PM, Jason A Ramsey wrote:
    > I have been struggling getting a HA iSCSI Target cluster in place for literally weeks. I cannot, for whatever reason, get pacemaker to create an iSCSILogicalUnit resource. The error message that I’m seeing leads me to believe that I’m missing something on the systems (“tcm_node”). Here are my setup commands leading up to seeing this error message:
    >
    > # pcs resource create hdcvbnas_tgtsvc ocf:heartbeat:iSCSITarget iqn="iqn.2016-07.local.hsinawsdev:hdcvadbs-witness" op monitor interval=15s
    >
    > # pcs resource create hdcvbnas_lun0 ocf:heartbeat:iSCSILogicalUnit target_iqn="iqn.2016-07.local.hsinawsdev:hdcvadbs-witness" lun="0" path=/dev/drbd1 implementation="lio" op monitor interval=15s
    >
    >
    > Failed Actions:
    > * hdcvbnas_lun0_stop_0 on hdc1anas002 'not installed' (5): call=321, status=complete, exitreason='Setup problem: couldn't find command: tcm_node',
    >      last-rc-change='Wed Jul 20 10:51:15 2016', queued=0ms, exec=32ms
    >
    > This is with the following installed:
    >
    > pacemaker-cli-1.1.13-10.el7.x86_64
    > pacemaker-1.1.13-10.el7.x86_64
    > pacemaker-libs-1.1.13-10.el7.x86_64
    > pacemaker-cluster-libs-1.1.13-10.el7.x86_64
    > corosynclib-2.3.4-7.el7.x86_64
    > corosync-2.3.4-7.el7.x86_64
    >
    > Please please please…any ideas are appreciated. I’ve exhausted all avenues of investigation at this point and don’t know what to do. Thank you!
    >
    > --
    >   
    > [ jR ]
    > @: jason at eramsey.org
    >   
    >    there is no path to greatness; greatness is the path
    >
    > _______________________________________________
    > Users mailing list: Users at clusterlabs.org
    > 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: Users at clusterlabs.org
    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