[ClusterLabs] HA iSCSITarget Using FileIO

[Jason A Ramsey]

Oh, and I forgot to add that when I try to create the LUN with the implementation=”lio” parameter, I see the following:

[root at hdc1anas002 ec2-user]# 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


[root at hdc1anas002 ec2-user]# pcs status
Cluster name: hdcvbnas
Last updated: Wed Jul 13 16:29:36 2016                     Last change: Wed Jul 13 16:29:33 2016 by root via cibadmin on hdc1anas002
Stack: corosync
Current DC: hdc1anas002 (version 1.1.13-10.el7-44eb2dd) - partition with quorum
2 nodes and 7 resources configured

Online: [ hdc1anas002 hdc1bnas002 ]

Full list of resources:

Master/Slave Set: hdcvbnas_tgtclone [hdcvbnas_tgt]
     Masters: [ hdc1anas002 ]
     Slaves: [ hdc1bnas002 ]
hdcvbnas_tgtfs   (ocf::heartbeat:Filesystem):            Started hdc1anas002
hdcvbnas_ip0      (ocf::heartbeat:IPaddr2): Started hdc1anas002
hdcvbnas_ip1      (ocf::heartbeat:IPaddr2): Started hdc1bnas002
hdcvbnas_tgtsvc                (ocf::heartbeat:iSCSITarget):          Started hdc1bnas002
hdcvbnas_lun0   (ocf::heartbeat:iSCSILogicalUnit):  FAILED hdc1anas002 (unmanaged)

Failed Actions:
* hdcvbnas_lun0_stop_0 on hdc1anas002 'not installed' (5): call=251, status=complete, exitreason='Setup problem: couldn't find command: tcm_node',
    last-rc-change='Wed Jul 13 16:29:33 2016', queued=0ms, exec=31ms


--

[ jR ]
  M: +1 (703) 628-2621
  @: jason at eramsey.org<mailto:jason at eramsey.org>

  there is no path to greatness; greatness is the path

From: Jason Ramsey <jason at eramsey.org>
Reply-To: Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
Date: Wednesday, July 13, 2016 at 4:02 PM
To: "users at clusterlabs.org" <users at clusterlabs.org>
Subject: [ClusterLabs] HA iSCSITarget Using FileIO

I’m having some difficulty setting up a PCS/Corosync HA iSCSI target. I’m able to create the iSCSI target resource (it spins up the target service properly when the pcs command is issued. However, when I attempt to create a LUN, I get nothing but error messages. This works:

pcs resource create hdcvbnas_tgtsvc ocf:heartbeat:iSCSITarget iqn=”iqn.2016-07.local.hsinawsdev:hdcvadbs-witness” op monitor interval=15s

But this does not:

pcs resource create hdcvbnas_tgtsvc ocf:heartbeat:iSCSITarget iqn=”iqn.2016-07.local.hsinawsdev:hdcvadbs-witness” implementation=”lio” portals=”10.0.96.100 10.0.96.101” op monitor interval=15s

Also, when the first (working) command is issued, the creation of the LUN does not:

pcs resource create hdcvbnas_lun0 ocf:heartbeat:iSCSILogicalUnit target_iqn=”iqn.2016-07.local.hsinawsdev:hdcvadbs-witness” lun=”0” path=/dev/drbd1 op monitor interval=15s

Here’s the results:

[root at hdc1anas002 ec2-user]# pcs status
Cluster name: hdcvbnas
Last updated: Wed Jul 13 15:59:05 2016                     Last change: Wed Jul 13 15:59:03 2016 by root via cibadmin on hdc1anas002
Stack: corosync
Current DC: hdc1anas002 (version 1.1.13-10.el7-44eb2dd) - partition with quorum
2 nodes and 7 resources configured

Online: [ hdc1anas002 hdc1bnas002 ]

Full list of resources:

Master/Slave Set: hdcvbnas_tgtclone [hdcvbnas_tgt]
     Masters: [ hdc1anas002 ]
     Slaves: [ hdc1bnas002 ]
hdcvbnas_tgtfs   (ocf::heartbeat:Filesystem):            Started hdc1anas002
hdcvbnas_ip0      (ocf::heartbeat:IPaddr2): Started hdc1anas002
hdcvbnas_ip1      (ocf::heartbeat:IPaddr2): Started hdc1bnas002
hdcvbnas_tgtsvc                (ocf::heartbeat:iSCSITarget):          Started hdc1bnas002
hdcvbnas_lun0   (ocf::heartbeat:iSCSILogicalUnit):  Stopped

Failed Actions:
* hdcvbnas_lun0_start_0 on hdc1anas002 'unknown error' (1): call=243, status=complete, exitreason='none',
    last-rc-change='Wed Jul 13 15:59:03 2016', queued=0ms, exec=123ms
* hdcvbnas_lun0_start_0 on hdc1bnas002 'unknown error' (1): call=257, status=complete, exitreason='none',
    last-rc-change='Wed Jul 13 15:59:03 2016', queued=0ms, exec=124ms


PCSD Status:
  hdc1anas002: Online
  hdc1bnas002: Online

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled


Unfortunately, neither the corosync nor syslog logs provide any information that is remotely helpful in troubleshooting this. I appreciate any help you might provide.

--

[ jR ]
  @: jason at eramsey.org<mailto:jason at eramsey.org>

  there is no path to greatness; greatness is the path
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20160713/655fa9a1/attachment-0002.html>