[ClusterLabs] iSCSITarget problems with just add an iqn

Strahil Nikolov hunter86_bg at yahoo.com
Thu Apr 2 13:29:46 EDT 2020

On April 2, 2020 3:39:07 PM GMT+03:00, Stefan K <shadow_7 at gmx.net> wrote:
>yesterday I wanted to ust add an iqn in my setup, it works 2times
>before, but yesterday it fails and I don't know why (I attached the log
>and config)..
>I use targetcli to configure iSCSI, with targetcli its possible to add
>an IQN on the fly.. pacemaker/ the iSCSITarget ressource don'tuse that,
>is it possible to change the script? Is it possible in pacemaker that I
>just get the changes and forward it to the iSCSIITarget?
>And last question, why stop/start pacemaker all ressouces and not just
>the ressource which was changed?
>thanks in advanced
>crm conf sh
>node 1: zfs-serv3 \
>        attributes
>node 2: zfs-serv4 \
>        attributes
>primitive ha-ip IPaddr2 \
>        params ip= cidr_netmask=24 nic=bond0 \
>        op start interval=0s timeout=20s \
>        op stop interval=0s timeout=20s \
>        op monitor interval=10s timeout=20s \
>        meta target-role=Started
>primitive iscsi-lun00 iSCSILogicalUnit \
>params implementation=lio-t
>lun=0 lio_iblock=0 scsi_sn=8a12f029
>path="/dev/zvol/vm_storage/zfs-vol1" \
>        meta
>primitive iscsi-lun01 iSCSILogicalUnit \
>params implementation=lio-t
>lun=1 lio_iblock=1 scsi_sn=f0e7a755
>path="/dev/zvol/vm_storage/zfs-vol2" \
>        meta
>primitive iscsi-lun02 iSCSILogicalUnit \
>params implementation=lio-t
>lun=2 lio_iblock=2 scsi_sn=6b45cc5f
>path="/dev/zvol/vm_storage/zfs-vol3" \
>        meta
>primitive iscsi-server iSCSITarget \
>params implementation=lio-t
>primitive resIPMI-zfs3 stonith:external/ipmi \
>params hostname=zfs-serv3 ipaddr= userid=stonith
>passwd=stonith_321 interface=lan priv=OPERATOR pcmk_delay_max=20 \
>        op monitor interval=60s \
>        meta
>primitive resIPMI-zfs4 stonith:external/ipmi \
>params hostname=zfs-serv4 ipaddr= userid=stonith
>passwd=stonith_321 interface=lan priv=OPERATOR pcmk_delay_max=20 \
>        op monitor interval=60s \
>        meta
>primitive vm_storage ZFS \
>        params pool=vm_storage importargs="-d /dev/disk/by-vdev/" \
>        op monitor interval=5s timeout=30s \
>        op start interval=0s timeout=90 \
>        op stop interval=0s timeout=90 \
>        meta target-role=Started
>location location-resIPMI-zfs3-zfs-serv3--INFINITY resIPMI-zfs3 -inf:
>location location-resIPMI-zfs4-zfs-serv4--INFINITY resIPMI-zfs4 -inf:
>colocation pcs_rsc_colocation_set_ha-ip_vm_storage_iscsi-server inf:
>ha-ip vm_storage iscsi-server iscsi-lun00 iscsi-lun01 iscsi-lun02
>order pcs_rsc_order_set_iscsi-server_vm_storage_ha-ip iscsi-server
>iscsi-lun00 iscsi-lun01 iscsi-lun02 ha-ip
>property cib-bootstrap-options: \
>        have-watchdog=false \
>        dc-version=1.1.16-94ff4df \
>        cluster-infrastructure=corosync \
>        cluster-name=zfs-vmstorage \
>        no-quorum-policy=stop \
>        stonith-enabled=true \
>        last-lrm-refresh=1585662940
>rsc_defaults rsc_defaults-options: \
>        resource-stickiness=100

Yes, you can add a new initiator live.

How did you add it (what command and it's  options)  ?

What is your OS (Distro,version)  and corosync/pacemaker versions ?

Best Regards,
Strahil Nikolov

More information about the Users mailing list