[ClusterLabs] ressources in an unmanaged status

Stefan K shadow_7 at gmx.net
Fri Nov 9 08:37:05 EST 2018


Hello,

I've the following setup:

crm conf sh
node 1: zfs-serv3 \
        attributes
node 2: zfs-serv4 \
        attributes maintenance=on
primitive ha-ip IPaddr2 \
        params ip=192.168.2.10 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 target_iqn="iqn.2003-01.org.linux-iscsi.vm-storage.x8664:sn.cf6fa665ec23" lun=0 lio_iblock=0 path="/dev/zvol/vm_storage/zfs-vol1"
primitive iscsi-lun01 iSCSILogicalUnit \
        params implementation=lio-t target_iqn="iqn.2003-01.org.linux-iscsi.vm-storage.x8664:sn.cf6fa665ec23" lun=1 lio_iblock=1 path="/dev/zvol/vm_storage/zfs-vol2"
primitive iscsi-lun02 iSCSILogicalUnit \
        params implementation=lio-t target_iqn="iqn.2003-01.org.linux-iscsi.vm-storage.x8664:sn.cf6fa665ec23" lun=2 lio_iblock=2 path="/dev/zvol/vm_storage/zfs-vol3"
primitive iscsi-server iSCSITarget \
        params implementation=lio-t iqn="iqn.2003-01.org.linux-iscsi.vm-storage.x8664:sn.cf6fa665ec23" portals="192.168.2.10:3260" allowed_initiators="iqn.1998-01.com.vmware:brainslug9-75488000 iqn.1998-01.com.vmware:brainslug8-05897000 iqn.1998-01.com.vmware:brainslug7-592b0000 iqn.1998-01.com.vmware:brainslug10-5564c000" \
        meta
primitive resIPMI-zfs3 stonith:external/ipmi \
        params hostname=zfs-serv3 ipaddr=172.xx.xx.xx userid=user passwd=pw interface=lan priv=OPERATOR pcmk_delay_max=20 \
        op monitor interval=60s \
        meta
primitive resIPMI-zfs4 stonith:external/ipmi \
        params hostname=zfs-serv4 ipaddr=172.xx.xx.xx userid=user passwd=pw 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: zfs-serv3
location location-resIPMI-zfs4-zfs-serv4--INFINITY resIPMI-zfs4 -inf: zfs-serv4
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_ha-ip_iscsi-server_vm_storage ha-ip:stop iscsi-lun00:stop iscsi-lun01:stop iscsi-lun02:stop iscsi-server:stop vm_storage:stop symmetrical=false
order pcs_rsc_order_set_iscsi-server_vm_storage_ha-ip vm_storage:start iscsi-server:start iscsi-lun00:start iscsi-lun01:start iscsi-lun02:start ha-ip:start symmetrical=false
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=1541768433
rsc_defaults rsc_defaults-options: \
        resource-stickiness=100


If I put a node into maintenance the ressources become unmanaged, If I shutdown a node the ressources will migrate correctly, can somebody tell me please what is wrong here? Here the logs from a node which I set to maintenance:

Nov 09 14:23:08 [30104] zfs-serv4       crmd:     info: crm_timer_popped:       PEngine Recheck Timer (I_PE_CALC) just popped (900000ms) 
Nov 09 14:23:36 [30103] zfs-serv4    pengine:   notice: process_pe_message:     Calculated transition 60, saving inputs in /var/lib/pacemaker/pengine/pe-input-336.bz2 
at the same time on the other node:
Nov 09 14:08:53 [9630] zfs-serv3        cib:     info: cib_process_ping:        Reporting our current digest to zfs-serv4: 81c440e08f9ab611967de64ba7b6ce46 for 0.270.0 (0x556faf4e9220 0) 

thanks for help!
best regards
Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181109/46bd945a/attachment-0001.html>


More information about the Users mailing list