[DRBD-user] [Pacemaker] Pacemaker unable to start DRBD

[Lars Ellenberg]

On Tue, Jul 24, 2018 at 07:27:28AM +0000, Jaco van Niekerk wrote:
> Hi
> 
> I am using the following packages:
> pcs-0.9.162-5.el7.centos.1.x86_64
> kmod-drbd84-8.4.11-1.el7_5.elrepo.x86_64
> drbd84-utils-9.3.1-1.el7.elrepo.x86_64
> pacemaker-1.1.18-11.el7_5.3.x86_64
> corosync-2.4.3-2.el7_5.1.x86_64
> targetcli-2.1.fb46-6.el7_5.noarch
> kernel-3.10.0-862.9.1.el7.x86_64
> 
> my /etc/drbd.conf
> global { usage-count no; }
> common { protocol C; }
> resource imagesdata {
>  on node1.san.localhost {
>   device /dev/drbd0;
>   disk   /dev/vg_drbd/lv_drbd;
>   address  192.168.0.2:7789;
>   meta-disk internal;
>  }
>  on node2.san.localhost {
>   device /dev/drbd0;
>   disk   /dev/vg_drbd/lv_drbd;
>   address  192.168.0.3:7789;
>   meta-disk internal;
>  }
> }
> 
> my /etc/corosync/corosync.conf:
> totem {
>     version: 2
>     secauth: off
>     cluster_name: san_cluster
>     transport: udpu
>     interface {
>         ringnumber: 0
>         bindnetaddr: 192.168.0.0
>         broadcast: yes
>         mcastport: 5405
>     }
> }
> 
> nodelist {
>     node {
>     ring0_addr: node1.san.localhost
>         name: node1
>         nodeid: 1
>     }
> 
>     node {
>     ring0_addr: node2.san.localhost
>         name: node2
>         nodeid: 2
>     }
> }
> 
> quorum {
>     provider: corosync_votequorum
>     two_node: 1
>     wait_for_all: 1
>     last_man_standing: 1
>     auto_tie_breaker: 0
> }
> 
> logging {
>     to_logfile: yes
>     logfile: /var/log/cluster/corosync.log
>     to_syslog: yes
> }
> 
> DRBD Starts perfectly fine and syncs as well.
> 
> Pacemaker setup:
> pcs cluster auth node1.san.localdomain node2.san.localdomain -u hacluster -p PASSWORD
> pcs cluster setup --name san_cluster node1.san.localdomain node2.san.localdomain
> pcs cluster start --all
> pcs cluster enable --all
> pcs property set stonith-enabled=false
> pcs property set no-quorum-policy=ignore
> 
> The following command doesn't work:
> pcs resource create my_iscsidata ocf:linbit:drbd drbd_resource=iscsidata op monitor interval=10s
> pcs resource master MyISCSIClone my_iscsidata master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true
> 
> I receive the following on pcs status:
> * my_iscsidata_monitor_0 on node2.san.localhost 'not configured' (6):
> call=9, status=complete, exitreason='meta parameter misconfigured,
> expected clone-max -le 2, but found unset.',

Well, yes, that is expected.

"Prepare" the pacemaker configuration in a "shadow cib",
then "commit" (or "cib push", in pcs speak) the finished config as one
into the live cib.

Don't take shortcuts omitting the "shadow cib".


-- 
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker

DRBD® and LINBIT® are registered trademarks of LINBIT
__
please don't Cc me, but send to list -- I'm subscribed